<div dir="ltr">Hi Tim, Jürgen and PSC,<br><div class="gmail_extra"><br></div><div class="gmail_extra">After reviewing this plan I have to say it is an excellent solution to a no-size-fits-all problem. Thank you for all the consideration and work you have put into it.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I now have a solid (and indeterminate :^) schedule to present to my employer, which will help them plan resources to fund further QGIS development.</div><div class="gmail_extra"><br></div><div class="gmail_extra">It will also help with planning on how/when to produce new nightlies for Mac.<br clear="all"><div><div class="gmail_signature"><br></div><div class="gmail_signature">Regards,</div><div class="gmail_signature"><br>Larry Shaffer</div><div class="gmail_signature">QGIS Support/Development | Boundless<br></div><div class="gmail_signature"><br>Dakota Cartography<br>Black Hills, South Dakota</div></div>
<br><div class="gmail_quote">On Mon, Feb 8, 2016 at 7:45 AM, Jürgen E. <span dir="ltr"><<a href="mailto:jef@norbit.de" target="_blank">jef@norbit.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi Tim,<br>
<span class=""><br>
On Mon, 08. Feb 2016 at 14:01:12 +0200, Tim Sutton wrote:<br>
> Thanks Andreas - I’ll just paraphrase the above as another note in the<br>
> article - should make things a bit clearer!<br>
<br>
</span>Yes. We do 2.16 with PyQt5/Python3 support next to the existing<br>
Qt4/PyQt4/Python2 and the existing and widely unused Qt5 support. So we have<br>
all the smooth, non-breaking steps in master. We'll still release using<br>
Qt4/PyQt4/Python2, so that all the plugins keep working. And people can<br>
complete stuff that they have already started working on.<br>
<br>
2.16 will be in the regular 4 months schedule.<br>
<br>
After 2.16 we branch off a qgis3 branch that gets the API changes. There we<br>
drop Qt4/PyQt4/Python2 support and switch to Qt5/PyQt5/Python3. Because we<br>
cannot really estimate if that takes 4, 8 or even more months, we'll work on<br>
that on a "release when ready" scheme an see how it goes and set a date when<br>
qgis3 stabilized.<br>
<br>
The qgis3 branch will be in development so at first we'll probably have<br>
something that doesn't build at all, requires dependencies that are not easy<br>
available or at least not available on all platforms, while we're at it.<br>
<br>
Because there might be stuff, that can't wait that long, we meanwhile keep<br>
master open for new features. The nightlies can keep on going without much<br>
effort and also regular releases could be done if necessary.<br>
<br>
But master should still considered a dead branch as we is relies on fading<br>
dependencies and it will be eventually be replaced by the qgis3 (no merge). So<br>
stuff added to master before will get lost, if it was not also merged or redone<br>
for qgis3. So people should think twice if they consider to do anything in<br>
master while we're at qgis3.<br>
<span class=""><font color="#888888"><br>
<br>
Jürgen<br>
<br>
--<br>
Jürgen E. Fischer norBIT GmbH Tel. <a href="tel:%2B49-4931-918175-31" value="+49493191817531">+49-4931-918175-31</a><br>
Dipl.-Inf. (FH) Rheinstraße 13 Fax. <a href="tel:%2B49-4931-918175-50" value="+49493191817550">+49-4931-918175-50</a><br>
Software Engineer D-26506 Norden <a href="http://www.norbit.de" rel="noreferrer" target="_blank">http://www.norbit.de</a><br>
QGIS release manager (PSC) Germany IRC: jef on FreeNode<br>
</font></span><br>_______________________________________________<br>
Qgis-psc mailing list<br>
<a href="mailto:Qgis-psc@lists.osgeo.org">Qgis-psc@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br></blockquote></div><br></div></div>