<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>Well - in my opinion, if we delay the feature freeze we also have to delay the release.</p>
<p>QGIS 3 still crashes several times a day (esp. if you work with editing, complex forms and PostgreSQL transaction mode). QGIS 3 is way more unstable than QGIS 2.18. We need at least 1.5 months, better 2 months between feature freeze and release. If we move feature freeze, say, until end of November, we can't release in December or we would loose the good reputation that QGIS built in the last couple of years.</p>
<p>That is just my personal opinion. I use QGIS 3 a lot - and it is not a pleasant piece of software currently, but a major source of headaches and grief, not because of UI or missing features, but because of all the crashes I often experience (and are often hard to reproduce and report).</p>
<p>Andreas</p>
<p>On 2017-11-06 13:17, Mathieu Pellerin wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div dir="auto">Hmm we just jumped from discussing feature freeze exception to delaying release, is that correct?
<div dir="auto"> </div>
<div dir="auto">Personally, I'm big +1 for feature freeze exceptions-only *if* release date remains achievable. If not, it seems there is a consensus on adding additional time to this dev cycle, which remains preferable to shipping 3.0 with crucial architectural changes and additions missing.</div>
<div dir="auto"> </div>
<div dir="auto">That said I'm a -1 to go into a "release whenever it's ready" mode without a firm agreed upon (delayed) release date.</div>
<div dir="auto"> </div>
<div dir="auto">M</div>
</div>
<div class="gmail_extra"><br />
<div class="gmail_quote">On Nov 6, 2017 6:59 PM, "Andreas Neumann" <<a href="mailto:a.neumann@carto.net">a.neumann@carto.net</a>> wrote:<br />
<blockquote class="gmail_quote" style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;">
<div 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 style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0;">
<p>Hi Jürgen,</p>
<br />
<div class="m_-8244592068978794613moz-cite-prefix">On 11/06/2017 11:17 AM, Jürgen E. Fischer wrote:</div>
<blockquote 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 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 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="m_-8244592068978794613mimeAttachmentHeader"></fieldset><br />
<pre>______________________________<wbr />_________________
QGIS-Developer mailing list
<a class="m_-8244592068978794613moz-txt-link-abbreviated" href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a>
List info: <a class="m_-8244592068978794613moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/<wbr />mailman/listinfo/qgis-<wbr />developer</a>
Unsubscribe: <a class="m_-8244592068978794613moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/<wbr />mailman/listinfo/qgis-<wbr />developer</a></pre>
</blockquote>
<br /><br />
<div class="m_-8244592068978794613pre" style="margin: 0; padding: 0; font-family: monospace;">______________________________<wbr />_________________<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/<wbr />mailman/listinfo/qgis-<wbr />developer</a><br /> Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/<wbr />mailman/listinfo/qgis-<wbr />developer</a></div>
</blockquote>
<p><br /></p>
</div>
<br />______________________________<wbr />_________________<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/<wbr />mailman/listinfo/qgis-<wbr />developer</a><br /> Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/<wbr />mailman/listinfo/qgis-<wbr />developer</a></blockquote>
</div>
</div>
</blockquote>
<p><br /></p>
</body></html>