[Qgis-psc] QGIS 2.18 bug fixing effort

[Jürgen E. Fischer]

Hi Nyall,

On Tue, 23. May 2017 at 18:25:20 +1000, Nyall Dawson wrote:
> On this note, I'd like to float the idea of some "thaw" time (say a
> week) from when a release is tagged before we actually finalise the
> release. I realise this adds administrative burden (mostly to Jürgen,
> sorry) and I'd welcome suggestions on how we could avoid this. But in
> general I think some short delay between when we consider a release is
> ready and when it actually becomes packaged and available would give
> time for testing the final pre-release candidate before the release is
> made.

Well, I build from tags (unless there are required fixes to build).  So
tagging is when packaging starts.  If there is a "thaw" time, it should be
before tagging/release.  Not sure how long that time should be.

A week?  Then we would have nightlies for the release, that could be tested,
potential bugs still be fixed, run to a nightly again, be verified and
still not delay the release.

But we do point releases every 4 weeks, so 1 week would be a lot of that.

Maybe it's just this point release that is special because of our bug fixing
effort.  Usually we just backport fixes that have been verified to work in
master (although that currently doesn't always work between 2.18 and master).
But then again 2.18.6 had a similar issue.



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 release manager (PSC)  Germany                    IRC: jef on FreeNode
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20170523/aeac82ed/attachment.sig>