<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 27 Oct 2017, at 23:25, Jürgen E. Fischer <<a href="mailto:jef@norbit.de" class="">jef@norbit.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Andreas,<br class=""><br class="">On Fri, 27. Oct 2017 at 17:58:05 +0200, Andreas Neumann wrote:<br class=""><blockquote type="cite" class="">As to reviewing the PR queue: no idea how much effort would mean, but it<br class="">would have to be done quickly (e.g. within the next week). Jürgen has to<br class="">comment on that. We can spend some money on getting the PRs reviewed, but I<br class="">would need an estimate (e.g. x days).<br class=""></blockquote><br class="">Not sure how. The rule is clear - feature freeze means no new features. So<br class="">all features have to be in (committed to master) prior to the freeze. There is<br class="">no rule for exceptions - or one that makes it my buck. I just fix the dates<br class="">after we discussed them, make the release (and package it).<br class=""><br class="">Core committers can commit anything they see fit prior to the freeze (they got<br class="">that privilege because we trust them). It's not required to run commits it<br class="">through PRs first or have PRs reviewed and/or merged by and other core<br class="">committer. If they still use a PR and get noone interested to review and<br class="">merge, they can still merge it themselves (no news is good news).<br class=""><br class="">If other contributors want PRs merged, they have to find a core committer to<br class="">merge it for them (rub them the right way, advertize it and get users to cheer,<br class="">hire them, whatever helps). We're not obligated to merge anything - or pay<br class="">someone to review them. But if it's a feature PR, it shall not be merged in<br class="">freeze. When the PR was filed doesn't matter.<br class=""><br class="">I didn't arbitrarily set the freeze date - actually originally 3.0 should be<br class="">released when ready and not on a fixed schedule. The date was requested and<br class="">suggested by the key people doing the work - and even already moved once as<br class="">their estimation was apparently too optimistic.<br class=""><br class="">The point of the freeze is to give us time to stabilize and fix bugs before the<br class="">release. We also discussed how much time is needed for that. Merging PRs<br class="">after the freeze would also require to discuss it's impact on the release date.<br class=""></div></div></blockquote><div><br class=""></div><div>I agree with what you say above (and I apologise if my original message sounded like I was trying to shift the freeze goal posts again). I’ll cope if our PR is not merged but I wonder in the longer term if the '(rub them the right way, advertize it and get users to cheer hire them, whatever helps)’ is working for us? Tthe fact that our PR queue is so long makes me think it would be worthwhile to treat managing the PR queue as a paid effort from QGIS side (after the freeze is lifted) - or otherwise come up with a system to deal with it more effectively….maybe a topic for Madeira anyway….bring on the freeze!</div><div><br class=""></div><div>Regards</div><div><br class=""></div><div>Tim</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""><br class="">Jürgen<br class=""><br class="">-- <br class="">Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31<br class="">Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50<br class="">Software Engineer D-26506 Norden <a href="http://www.norbit.de" class="">http://www.norbit.de</a><br class="">QGIS release manager (PSC) Germany IRC: jef on FreeNode<br class="">_______________________________________________<br class="">QGIS-Developer mailing list<br class=""><a href="mailto:QGIS-Developer@lists.osgeo.org" class="">QGIS-Developer@lists.osgeo.org</a><br class="">List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer<br class="">Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer</div></div></blockquote></div><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="430A1CBC-882C-4405-9F38-3C56F1E118A6" src="cid:B67F6A36-B856-4FD5-91BC-5BDE8990D373" class=""></span><div style="color: rgb(0, 0, 0); font-family: Helvetica; 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; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="font-weight: normal;" class=""><br class="Apple-interchange-newline"><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">---</div><div style="font-weight: normal;" class=""><br class=""></div><div class=""><b class="">Tim Sutton</b></div><div style="font-weight: normal;" class="">QGIS Project Steering Committee Chair</div><div style="font-weight: normal;" class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a></div><div style="font-weight: normal;" class=""><br class=""></div></div><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; 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; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal;"><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; 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; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;">
</div>
<br class=""></body></html>