Re: 3.0 Release plans

On 12 Apr 2013 at 9:42, Simon Larochelle wrote:

> 
> This sounds like a good plan. It would be nice to fix two build issues
> on windows (bugs 13030 and 13389) before the official 3.0 release. Are
> there any GSOC candidates willing to work on these bugs?

It would be nice to get these fixed, indeed. 
Our current policy of only using ming32-built 3rd-part libraries from the
opensuse repositories don't seem to work too well in practice.

Other windows bugs that might be worth looking into:


11329: 3rd-part libraries that don't work on win2000. Given the age of
win2000, I'd say drop support for it. This means changing the "supported
systems" page, and perhaps adding some nsis script magic that says that
2000 and earlier are not supported.

12247: We seem to be distributing an old version of the msvc 2008 runtime
installer. That needs to be updated, and some nsis script magic added that
loops through a lot of registry entries to check if a newer version is
already installed. Each version writes a different entry that looks like
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{NNN
NNNN-NNN-NNN-NNNN-NNNNNNNNNNNN}], so just one regcheck is not enough, a loop is 
needed. 
At the minimum, the vcredist file should be updated, link included in bugreport.

13479: We have gotten some installer translations in UTF-8 format, but the version of NSIS 
used by the person who built 2.9.4 does not understand UTF-8, making every non-ascii 
character show up broken. I made a patch that adds a check for unicode compliance, but 
I'm not sure it's failsafe enough.

Anyone who knows the nsis script language enough here?