Hi PSC,<br>
<br>
Thank you very much for taking a decision, that will help very much to get ahead!<br>
<br>
Just one question, did you evaluate to switch master with a qgis2 branch and qgis3 with master? So basically the same schema but with renamed branches.<br>
IMHO that would make it clearer that devs are encouraged to work on qgis 3 and we would not have to "replace" a branch but instead just retire the qgis2 branch once the release happened.<br>
<br>
Thanks again and best wishes<br>
<br>
Matthias<br>
<br>
On February 9, 2016 11:30:28 AM GMT+01:00, Tim Sutton <tim@kartoza.com> wrote:<br>
>Hi<br>
><br>
><br>
>On Tue, Feb 9, 2016 at 2:58 AM, Larry Shaffer <larrys@dakotacarto.com><br>
>wrote:<br>
><br>
>> Hi Tim, Jürgen and PSC,<br>
>><br>
>> After reviewing this plan I have to say it is an excellent solution<br>
>to a<br>
>> no-size-fits-all problem. Thank you for all the consideration and<br>
>work you<br>
>> have put into it.<br>
>><br>
>> I now have a solid (and indeterminate :^) schedule to present to my<br>
>> employer, which will help them plan resources to fund further QGIS<br>
>> development.<br>
>><br>
>> It will also help with planning on how/when to produce new nightlies<br>
>for<br>
>> Mac.<br>
>><br>
><br>
>Thanks Larry - I will post my blog post summarising everything tonight<br>
>(including salient bits from the above discussion). Yes its<br>
>interterminate,<br>
>but I think the general aim is still to try to encourage everyone to<br>
>get it<br>
>ready for 1 year from now (as much as we can).<br>
><br>
>Regards<br>
><br>
>Tim<br>
><br>
><br>
><br>
>><br>
>> Regards,<br>
>><br>
>> Larry Shaffer<br>
>> QGIS Support/Development | Boundless<br>
>><br>
>> Dakota Cartography<br>
>> Black Hills, South Dakota<br>
>><br>
>> On Mon, Feb 8, 2016 at 7:45 AM, Jürgen E. <jef@norbit.de> wrote:<br>
>><br>
>>> Hi Tim,<br>
>>><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<br>
>the<br>
>>> > article - should make things a bit clearer!<br>
>>><br>
>>> 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. <br>
>So we<br>
>>> have<br>
>>> all the smooth, non-breaking steps in master. We'll still release<br>
>using<br>
>>> Qt4/PyQt4/Python2, so that all the plugins keep working. And people<br>
>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. <br>
>There<br>
>>> we<br>
>>> drop Qt4/PyQt4/Python2 support and switch to Qt5/PyQt5/Python3. <br>
>Because<br>
>>> we<br>
>>> cannot really estimate if that takes 4, 8 or even more months, we'll<br>
>work<br>
>>> on<br>
>>> that on a "release when ready" scheme an see how it goes and set a<br>
>date<br>
>>> when<br>
>>> qgis3 stabilized.<br>
>>><br>
>>> The qgis3 branch will be in development so at first we'll probably<br>
>have<br>
>>> something that doesn't build at all, requires dependencies that are<br>
>not<br>
>>> easy<br>
>>> available or at least not available on all platforms, while we're at<br>
>it.<br>
>>><br>
>>> Because there might be stuff, that can't wait that long, we<br>
>meanwhile keep<br>
>>> master open for new features. The nightlies can keep on going<br>
>without<br>
>>> 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<br>
>fading<br>
>>> dependencies and it will be eventually be replaced by the qgis3 (no<br>
>>> merge). So<br>
>>> stuff added to master before will get lost, if it was not also<br>
>merged or<br>
>>> redone<br>
>>> for qgis3. So people should think twice if they consider to do<br>
>anything<br>
>>> in<br>
>>> master while we're at qgis3.<br>
>>><br>
>>><br>
>>> Jürgen<br>
>>><br>
>>> --<br>
>>> Jürgen E. Fischer norBIT GmbH Tel.<br>
>>> +49-4931-918175-31<br>
>>> Dipl.-Inf. (FH) Rheinstraße 13 Fax.<br>
>>> +49-4931-918175-50<br>
>>> Software Engineer D-26506 Norden<br>
>>> <a href="http://www.norbit.de">http://www.norbit.de</a><br>
>>> QGIS release manager (PSC) Germany IRC: jef on<br>
>>> FreeNode<br>
>>><br>
>>> _______________________________________________<br>
>>> Qgis-psc mailing list<br>
>>> Qgis-psc@lists.osgeo.org<br>
>>> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-psc">http://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br>
>>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Qgis-psc mailing list<br>
>> Qgis-psc@lists.osgeo.org<br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-psc">http://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br>
>><br>
><br>
><br>
><br>
>-- <br>
>------------------------------------------------------------------------------------------<br>
>Tim Sutton<br>
>Visit <a href="http://kartoza.com">http://kartoza.com</a> to find out about open source:<br>
> * Desktop GIS programming services<br>
> * Geospatial web development<br>
>* GIS Training<br>
>* Consulting Services<br>
>Skype: timlinux Irc: timlinux on #qgis at <a href="http://freenode.net">freenode.net</a><br>
>Tim is a member of the QGIS Project Steering Committee<br>
>-------------------------------------------------------------------------------------------<br>
>Kartoza is a merger between Linfiniti and Afrispatial<br>
><br>
><br>
>------------------------------------------------------------------------<br>
><br>
>_______________________________________________<br>
>Qgis-psc mailing list<br>
>Qgis-psc@lists.osgeo.org<br>
><a href="http://lists.osgeo.org/mailman/listinfo/qgis-psc">http://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br>
<br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.<br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.