[Qgis-developer] Post-release period of portable commits only?

Ivan Mincik ivan.mincik at gmail.com
Mon Feb 24 08:23:55 PST 2014

Hash: SHA1

> Ok, seriously, I should probably emphasize in the freeze announcement,
> that it's mainly the users that are supposed to test the daily prereleases
> and weekly release candidates and report problems, while the developers
> work on reproducing and fixing already known or newly reported bugs.
> And the warnings on the download page should be changed to say, that
> testing nightly builds in the development phase are different thing than
> the daily prereleases in the freeze phase.
> Jürgen

Jürgen, at first thank you for your work as a developer and RM.

Time based releases are very good decision.

I think that clear separation of nightly builds after a feature freeze from
regular nightly builds (even if they are technically same) followed by loud
public announcements will surely help to catch more bugs.

Even if there is a no man power to maintain bugfix releases, please support
people to commit backported fixes to release branches. I think many people
realized importance of these bug releases and will offer a hand. I vote for
Sandro's work flow - if there is at least one commit from latest minor release
and at least 14 days of silence - release just a source code. Other things
will follow upon volunteer base.

- -- 
Ivan Minčík
ivan.mincik at gmail.com   GPG: 0x79529A1E  http://imincik.github.io/0x79529A1E.key
ivan.mincik at gista.sk    GPG: 0xD714B02C  http://imincik.github.io/0xD714B02C.key
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/


More information about the Qgis-developer mailing list