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

[Matthias Kuhn]

Hi Tim

On 11/06/2017 01:57 PM, Tim Sutton wrote:
> Hi
>
>> On 06 Nov 2017, at 12:00, Matthias Kuhn <matthias at opengis.ch
>> <mailto:matthias at opengis.ch>> wrote:
>>
>> Hi Tim,
>>
>> Thanks for raising this, I think it's very important to have everyone
>> on board and especially have Jürgen as Release Manager agree on the plan.
>>
>> For what I think, the 3.0 release is a very special release since we
>> have the unique possibility to work on the API and to some degree on
>> workflows. Actually this is in my opinion not only a possibility but
>> an obligation as we will severely disappoint plugin developers and
>> users if we break things again in the near future.
>>
>> The calls for exemption that we have now are mostly backed up with
>> the argument that right now is the right time to do certain things.
>> This argument can not be repeated for future 3.x releases. I would
>> therefore propose not to discuss the fixed release schedule in
>> general, it has IMO worked out quite nicely. Instead I would like the
>> PSC to discuss a flexible handling of this particular major release
>> with the very specific requirements.
>>
>
> Thanks for your reply Matthias. Sorry I was unclear - 100% agreed that
> we should see the regular 4 month release cycle in place - I intended
> ‘release when it’s ready’ to apply only to QGIS 3.0. We basically go
> into a mode where we are in ‘soft freeze’ - where there should be
> agreement before merging PR’s and when we agree (e.g. by monthly vote)
> that all exceptions are done, we enter a formal freeze. 
>

Thanks Tim, that sounds like a good path forward. To avoid being in this
state for too long I'd prefer to go for 2 weeks instead of a month and
agree beforehand on what needs to be done. This way we also have a clear
list of criteria for decision making.

Regards
Matthias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20171106/6a99d6c3/attachment.html>