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

[Mathieu Pellerin]

Nightly builds (or weekly snapshots for that matter) are very different
from a publicized, pre-release preview build. With a prepared pre-release
preview, users are at least expecting that basic functioning will work,
that's something  the nightly builds simply can't guarantee by the nature
of what those are. Very few average user will install a nightly development
build, but you get an higher chance of getting a broader number of people
(that interacts with QGIS in different ways) to test out your product
before it's released.

It also helps channel what your describing as noise (i.e. users running
into problems) into a better managed call for people to test and report.
The noise will happen no matter what. But it might make some sense to
trigger some of that noise (valid bugs and "invalid" RTFM cases) _before_
you release your final version via a pre-release social media and news site
"try this pre-release build" :)

It's really more a matter of presentation to the users than of actual work.
As you point out Jef, you guys already have the infrastructure that
produces weekly standalone builds, and daily packages.

Math





On Mon, Feb 24, 2014 at 2:40 PM, Jürgen E. <jef at norbit.de> wrote:

> 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
>
> --
> 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
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20140224/fab54023/attachment-0001.html>