[QGIS-Developer] PROPOSAL: change how we manage the 3.0 release process

[Andreas Neumann]

It would be nice if the core devs could agree on items that need to go
into 3.0 before feature freeze - so we don't have to delay longer than
necessary. 

The other question is how to deal with features that could also be done
in 3.2. Can they also go into 3.0 if they are ready before the feature
freeze? In other words: do we already have a feature freeze but allow
exceptions where core devs agree on? Or will the whole feature freeze be
delayed? 

Andreas 

On 2017-11-06 12:23, Matthias Kuhn wrote:

> Hi Jürgen, 
> On 11/06/2017 11:17 AM, Jürgen E. Fischer wrote: 
> 
> Hi Matthias,
> 
> On Mon, 06. Nov 2017 at 11:00:04 +0100, Matthias Kuhn wrote:
> 
> Instead I would like the PSC to discuss a flexible handling of this
> particular major release with the very specific requirements.
> 
> The "release when ready" policy was made for 3.0 and only for 3.0.  The plan is
> to return to the original way of doing release afterwards.
> 
> That would have been my preference anyway and returning to it is ok with me.

Nice, looks like everyone agrees.
Can we schedule a release-plan meeting with involved devs to discuss
if/when it's ready?

Thanks a lot
Matthias

> Although IIRC the move to a fixed date was made because others argued that they
> need to communicate a date to their customers.
> 
> Jürgen
> 
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

_______________________________________________
QGIS-Developer mailing list
QGIS-Developer at lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20171106/1ba5c82e/attachment-0001.html>