<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi<div class=""><br class=""><blockquote type="cite" class="">On 13 May 2016, at 11:41, Jürgen E. Fischer <<a href="mailto:jef@norbit.de" class="">jef@norbit.de</a>> wrote:<br class=""><br class="">Hi Tim,<br class=""><br class="">On Fri, 13. May 2016 at 08:37:37 +0200, Tim Sutton wrote:<br class=""><blockquote type="cite" class="">I think we should let Jürgen make the call since he has the best<br class="">understanding of the impacts of delaying it.<br class=""></blockquote><br class="">Well, it's not a problem to run release.pl two weeks later. But:<br class=""><br class="">I currently face a problem with a bigger project, where chances are high that I<br class="">can't do it in time for 2.16 (at least not feature complete; even not with the<br class="">extra week - not counting Girona).<br class=""><br class="">That brought me to look at our discussion about the 3.0 - which's outcome you<br class="">summarized on <a href="http://blog.qgis.org/2016/02/10/qgis-3-0-plans/" class="">http://blog.qgis.org/2016/02/10/qgis-3-0-plans/</a>.<br class=""><br class="">At the time I didn't anticipate that I would have this problem and therefore<br class="">wanted more to discourage continuing work on the master branch and not<br class="">emphasize the possibility of more 2.x releases, while everyone else works on<br class="">the qgis3 branch.<br class=""><br class="">But new releases are planned<br class=""><a href="http://qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule" class="">http://qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule</a><br class="">it's just not clear if those are 2.x or 3.x releases yet.<br class=""><br class="">So I'll probably need to put my stuff into master and qgis3 after feature<br class="">freeze. So the rule "if you can't make into this slot, use the next - which is<br class="">soon" still applies. Although theoretically there still is a chance that won't<br class="">be a 2.18 release, because if we manage get qgis3 into shape very quickly the<br class="">slot will be taken by the first 3.x release.<br class=""><br class="">But we want to concentrate on qgis3 after 2.16 - so it might be still worth to<br class="">make an exception here - so at least most people can move there full focus to<br class="">3.0 after 2.16 - because they could finish what they needed to have in a<br class="">release within the additional two weeks and don't need to worry about master<br class="">afterwards (until qgis3 is merged back).<br class=""><br class=""></blockquote><div class=""><br class=""></div><blockquote type="cite" class="">But is that more important than keeping credibility?<br class=""><br class=""></blockquote><div class=""><br class=""></div><div class=""><br class="">So my feeling is that credibility comes from communicating clearly our plans and what is going on, not from having an unwavering approach with no flexibility. So as the Release Manager I would be quite OK with you sending out a message saying:</div><div class=""><br class=""></div><div class="">* QGIS 3.0 is scheduled for XXX and will be based on Qt5. The release may be subject to delays if we are not satisfied with the stability.</div><div class="">* QGIS 2.16 is scheduled for YYY and will be based on Qt5</div><div class="">* QGIS 2.18 will be scheduled for ZZZ if QGIS has not been released by XXX.</div><div class=""><br class=""></div><div class="">Or some variant of that. I wouldn’t even mind if both QGIS 3 and QGIS 2.18 are released at the same time given the somewhat unknown quantity that the QGIS 3 release is going to be others may appreciate that too. My mistake in those previous discussions was not letting you (as Release Manager) set the agenda, so thats something we can avoid this time around and not make this a committee decision :-P</div><div class=""><br class=""></div><div class="">Anyway thats my 2c.</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Tim</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><blockquote type="cite" class="">Not sure - I'm fine with both.<br 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-psc mailing list<br class=""><a href="mailto:Qgis-psc@lists.osgeo.org" class="">Qgis-psc@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/qgis-psc<br class=""></blockquote><br class=""><div class=""><span>—</span><br class=""><br class=""><br class=""><span><img height="118" width="150" apple-inline="yes" id="EBC798E3-D41E-4620-8BEB-59840EC701D6" apple-width="yes" apple-height="yes" src="cid:1A5DF6DE-E302-4C28-BFBD-29663CBF1351" class=""></span><br class=""><br class=""><br class=""><br class="">Tim Sutton<br class=""><br class="">Co-founder: Kartoza<br class="">Project chair: <a href="http://qgis.org" class="">QGIS.org</a><br class=""><br class="">Visit http://kartoza.com to find out about open source:<br class=""><br class="">Desktop GIS programming services<br class="">Geospatial web development<br class="">GIS Training<br class="">Consulting Services<br class=""><br class="">Skype: timlinux <br class="">IRC: timlinux on #qgis at freenode.net<br class=""><br class=""><br class="">Kartoza is a merger between Linfiniti and Afrispatial<br class=""></div><br class=""></div></body></html>