[Qgis-psc] Draft announcement re 3.0

[Tim Sutton]

Hi

On Mon, Feb 8, 2016 at 11:45 AM, Nathan Woodrow <madmanwoo at gmail.com> wrote:

> IMO we should just branch now if we are doing it this way.  The sooner the
> better as it will give us more time to prep.
>
​Yes except I think Matthias wanted the 2.16 release (with its wrappers
etc.) to for the basis for 3.0. If that isnt important then no problem from
me to branch now already.

Regards

Tim​




>
> On Mon, 8 Feb 2016 7:40 pm Tim Sutton <tim at kartoza.com> wrote:
>
>> Hi
>>
>> On Mon, Feb 8, 2016 at 11:03 AM, Richard Duivenvoorde <richard at duif.net>
>> wrote:
>>
>>> On 07-02-16 22:56, Tim Sutton wrote:
>>> > Hi PSC> I have written up a draft announcement about the 3.0 plan. I am
>>> > including a complete draft below.. Please let me know if you have
>>> > comments, corrections, additions to this DRAFT so that I can post it
>>> and
>>> > then advertise it more broadly.
>>>
>>>
>>> Nice writing as always Tim! Thanks for this.
>>>
>>>
>> ​No problem!​
>>
>>
>>
>>> To me it is not fully clear in this text if we will branch 2.14 or 2.16,
>>> I think that is because (in Juergens words) in the beginning we talk
>>> about branch in parallel (which at least in my eyes is about branching
>>> now). But in the disadvantages part we write : "To counter this, our
>>> public recommendation is that after 2.16 comes out..."
>>>
>>> If we are not branching 2.14, we could mention the reason we are NOT
>>> branching now already (paid features/contracts?). I'm afraid some will
>>> be disappointed that they have to wait another half year before they can
>>> add the things they want to add/change.
>>>
>>>
>> ​My understanding (correct me if I am wrong Jürgen) is that we will do
>> nothing different for 2.x releases. I think the simplest way to explain it
>> is that we just 'keep on trucking', doing 2.x releases​ as 'normal' every 4
>> months until 3.0 is ready. After 2.16 is released, we immediately create
>> teh 3.0 branch and encourage all new features to be written there.
>>
>> Regards
>>
>> Tim
>>
>>
>>
>>> Regards,
>>>
>>> Richard
>>>
>>> PS I still think branching NOW is best: if no one will do anything, we
>>> will have a branch where nothing happens, but if dev's start
>>> working/testing ( at least I will try to build :-) ) we will have a
>>> headstart or at least some experience.
>>>
>>> _______________________________________________
>>> Qgis-psc mailing list
>>> Qgis-psc at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/qgis-psc
>>>
>>
>>
>>
>> --
>>
>> ------------------------------------------------------------------------------------------
>> Tim Sutton
>> Visit http://kartoza.com to find out about open source:
>>  * Desktop GIS programming services
>>  * Geospatial web development
>> * GIS Training
>> * Consulting Services
>> Skype: timlinux Irc: timlinux on #qgis at freenode.net
>> Tim is a member of the QGIS Project Steering Committee
>>
>> -------------------------------------------------------------------------------------------
>> Kartoza is a merger between Linfiniti and Afrispatial
>> _______________________________________________
>> Qgis-psc mailing list
>> Qgis-psc at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-psc
>
>


-- 
------------------------------------------------------------------------------------------
Tim Sutton
Visit http://kartoza.com to find out about open source:
 * Desktop GIS programming services
 * Geospatial web development
* GIS Training
* Consulting Services
Skype: timlinux Irc: timlinux on #qgis at freenode.net
Tim is a member of the QGIS Project Steering Committee
-------------------------------------------------------------------------------------------
Kartoza is a merger between Linfiniti and Afrispatial
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20160208/379f7ff7/attachment.html>