<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi All <br class=""><br class="">As discussed earlier, we raised the issue of when and how to freeze at the PSC meeting. We tried to take on board your various comments and came out with this recommendation:<br class=""><br class="">• The current master branch will be in ‘soft freeze’ with a list of allowed PR’s / Future PR’s related to these features:<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Datum transform handling (<a href="https://github.com/qgis/QGIS/pull/5535" class="">https://github.com/qgis/QGIS/pull/5535</a>)<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• SAGA Support (https://github.com/qgis/QGIS/pull/5155)<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• GRASS Support (https://github.com/qgis/QGIS/pull/5426)<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Metadata write support to file system (https://github.com/qgis/QGIS/pull/5379)<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• UI Widgets for drag forms (https://github.com/qgis/QGIS/pull/5467)<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>* Composer refactor ( https://github.com/qgis/QGIS/pull/5486 to drop bindings and new PR to come for composer refactor).<div class=""><br class=""></div><div class="">Please let us know if there were other ‘must merge’ features that were discussed but that I missed in the list above.<br class=""><br class=""><div class="">• We will hold a rolling vote put to core developer (on loomio.org) every two weeks (starting two weeks from now) with a simple question “shall we freeze”? Once we have quorum on that vote, we go ahead and freeze and Jürgen can pretty much ignore 3.x in his release planning until that vote passes. <br class=""></div><div class="">• The paid bug fixing should commence now already regardless of when the freeze will actually happen.<br class=""></div><div class=""><br class=""></div><br class="">To address specifically Mathieu’s concerns about an unspecified date in the future, we do not anticipate an endless feature frenzy - the ‘soft freeze’ should keep the timelines reasonable while still giving us a chance to make sure that they API changes get a chance to land.<div class=""><br class=""></div><div class=""><br class=""></div><div class="">I hope that woks for the majority of you. If you want o make the release come faster, help by reviewing code in PR’s, testing new features and generally pointing the QGIS car towards the finish line!</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Tim<br class=""><br class=""><br class=""><br class=""><div class=""><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;"> </span><span><img apple-inline="yes" id="ADB1FF0B-7851-47F4-B9CB-8A2FECB4D090" src="cid:B67F6A36-B856-4FD5-91BC-5BDE8990D373" class=""></span><br class=""><br class=""><br class=""><br class="">---<br class=""><br class="">Tim Sutton<br class="">QGIS Project Steering Committee Chair<br class="">tim@qgis.org<br class=""><br class=""><br class=""><br class=""></div><br class=""></div></div></body></html>