On 01/03/15 19:02, Markus Neteler wrote:
Hi,
On Tue, Feb 17, 2015 at 1:54 PM, Markus Neteler <[email protected]> wrote:
On Fri, Jun 20, 2014 at 3:39 AM, Scott Mitchell <[email protected]> wrote:
Agreed, and I like Markus’ idea of testing it on an upcoming release.
(just a low priority comment here)
While doing so it turns out that one week between RC2 and final is a bit short.
And some urgent fixes came in only during the RC procedure. We need to
[add] a phrase if this requires a new RC (not this time though!) or not
or depends.
Overall, we got the release out :-)
Any opinions on above remaining issue?
I think that with time we will get better at this procedure and the one
week limit should be ok, but I have no objections to add a phrase to
step 6 such as
"A final, concerted bug squashing effort by all developers of no more
than one week. During that same time the release announcement is
drafted. If an important bug is discovered for which a fix needs some
more testing, an RC3 can exceptionally be published, with another week
of testing before final release."
Moritz
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
