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

Jürgen E. Fischer jef at norbit.de
Sun Feb 23 23:40:42 PST 2014

Hi Mathieu,

On Mon, 24. Feb 2014 at 09:17:11 +0700, Mathieu Pellerin wrote:
> That reminds me of someone mentioning in a ticket of a 2.0 issue resolved
> against qgis 2.1 that he'd wait (angrily?) having fix backported into a
> (mythical) 2.0.x update rather than him moving to 2.2 and having to deal
> with possible regressions. I was thinking at the time that this sounds to
> me like a flawed behavior by some QGIS users, an egg or chicken situation.
> How are regressions fixed if users are not doing their parts in uncovering
> and reporting them.
> That led me to think there might be a very low-cost, high reward behavior
> QGIS could adopt: 4, or 2, weeks before the release date, {beta,release
> candidate,tech preview,etc.} builds (from master, no need to branch out
> really) are pushed out to osgeo4w & linux and quite loudly advertised (blog
> posts, social media, etc.) to get as many users as possible to test drive
> it. The users' feedback would enrich the 4-weeks period when developers are
> to be focused on bug-fixing only.
> Thoughts? Was that already suggested and declined?

What's the difference to the nightly builds and the weekly standalone snapshot
for Windows - except for the noise of course?


Jürgen E. Fischer         norBIT GmbH               Tel. +49-4931-918175-31
Dipl.-Inf. (FH)           Rheinstraße 13            Fax. +49-4931-918175-50
Software Engineer         D-26506 Norden               http://www.norbit.de
QGIS PSC member (RM)      Germany                      IRC: jef on FreeNode                         

norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

More information about the Qgis-developer mailing list