<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>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.</p>
<p>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?</p>
<p>Andreas</p>
<p>On 2017-11-06 12:23, Matthias Kuhn wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --> <!-- head ignored --><!-- meta ignored -->
<p>Hi Jürgen,</p>
<br />
<div class="moz-cite-prefix">On 11/06/2017 11:17 AM, Jürgen E. Fischer wrote:</div>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<pre>Hi Matthias,
On Mon, 06. Nov 2017 at 11:00:04 +0100, Matthias Kuhn wrote:
</pre>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<pre>Instead I would like the PSC to discuss a flexible handling of this
particular major release with the very specific requirements.
</pre>
</blockquote>
<pre>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.</pre>
</blockquote>
<br /> Nice, looks like everyone agrees.<br /> Can we schedule a release-plan meeting with involved devs to discuss if/when it's ready?<br /> <br /> Thanks a lot<br /> Matthias<br /> <br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<pre>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
</pre>
<br /><fieldset class="mimeAttachmentHeader"></fieldset><br />
<pre>_______________________________________________
QGIS-Developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
<br /><!-- html ignored --><br />
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">_______________________________________________<br /> QGIS-Developer mailing list<br /> <a href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a><br /> List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br /> Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></div>
</blockquote>
<p><br /></p>
</body></html>