Announcing release candidates

[someguy]

Wouldn't this be a good place to announce new release candidates? True, we can compulsively check Jenkins every few hours, and eventually a new build might appear on the Downloads page. But if the developers would drop a little note right here about what was changed, we could decide whether to download yet-another-gigabyte-plus, then migrate all of our customized files to a new installation, so we can help with testing.

From the sparse notes on Jenkins, it looks like every fix specific to Windows systems will also trigger a new Mac build. RC2 and RC3 have the same timestamp. Some mirrors have RC4, others do not. Honestly, I don't know what to make of it all.

[Johan G]

That is a very good point, and I fully agree. It would also be nice to know what things are supposed to be fixed between the release candidates (I honestly does not know by looking in the bug tracker).

Another thing: When people report the problems with a release candidate, could they please also report which release candidate they had those problems with. This could be useful not only for the developers, but for us other users as well. Personally I have used the version number in the name of the package (for example 3.0.0-rc1, which I am still running).