Looking ahead to 0.4.4

[Automate]

It's great to see all the development going on and the 0.4.4 issues list getting shorter.

I think it would be good to have a target date for the release of 0.4.4 so people can decide if they can get there changes in 0.4.4 or wait till 0.4.5

Is Mat going to be available to update the installer or does someone else need to take on that task?

[bwoodworth]

I would like to set a date for v0.4.4 pretty soon, but need to give developers time to update their plugins for the new logging method. End of February, might be a good date.

Mat is available to work on the installers for the next release.

[Automate]

OK, I thought you made it so the old logger calls would still work. You just got a obsolete message in Visual Studio.

[bwoodworth]

Yes, I will leave it in the API as obsolete, but with moving the event and debug logging if any plugin uses those they will need to be rebuilt.

[Automate]

There is an issue with UltiDev on Windows 8.1 http://ultidev.com/Forums/yaf_postst142 ... 1-Bug.aspx

It would be nice to get the new version in the OSA 0.4.4 install.

[tommysharp]

Any news on a date for the next release?

[Automate]

My vote is to go back to the previous NSIS installer unless we can get a couple problems resolved with the current one.

1. If you have any problems during the install, the installer removes everything so you have no OSA software left on the computer. This make it difficult to do any further troubleshooting of the OSA problem.
2. After a successful install, Windows will try and overwrite any files that are newer than the ones included in the installer. This causes problems if you try to update any of the plugins that are included in the installer such as the web server.

[Mat]

Hi Automate,

Stick any issues you have in Github against the installer so they can be tracked. For a bit more clarity, if the installer fails during an upgrade it will not remove the software it will roll back to the previously installed version as it is transactional. For a fresh install it will remove the components it installed. This does overcome previous issues where users had an issue during the first install and when they tried subsequently it would fail as bits were left over from the last attempt.

The only scenario i can think of where windows will overwrite the files (plugins) is when using windows restore points as it will roll the files back to a known good state. If you know of other scenarios causing issues stick them in GITHUB to be looked at.

There is currently only 2 issues against the installer and I think both have been done but not closed.

[Vaughn]

Yay Matt!

I have been working hard on content for this release and was not looking forward to figuring out how to get it out too. Although I would like to get more involved in it.

Well, I will work on cleaning up my latest changes and general little things and try to get the code ready for packaging.

Vaughn

[Automate]

Hi, Mat, good to see you in the forum.

For a bit more clarity, if the installer fails during an upgrade it will not remove the software it will roll back to the previously installed version as it is transactional. For a fresh install it will remove the components it installed.

Usually when this happens it is on a new install. Here is the latest example but there have been many in the forums. http://www.opensourceautomation.com/php ... t1109.html

Maybe the installer could ask the user whether to roll back or not.