[Qgis-developer] Release schedule discussion - again

[Nyall Dawson]

On 14 October 2015 at 17:25, Nathan Woodrow <madmanwoo at gmail.com> wrote:
> When we want to move to 3.0 it has to be planned out well and documented.
> There is going to be API breaks on a lot of different fronts, which might
> mean it might be best to hold that release off for 12 months while
> everything is sorted and people have time to catch up. As it will break
> plugins again this isn't something we should just drop and hope that it
> sorts it self out.

I honestly don't think we have the luxury of that time frame. Sooner
or later, Qt4 will break on one of our platforms, and that will be a
worse situation for users than some missing plugins. To put this in
perspective, Qt4 IS BROKEN on the latest OSX release and can only be
used with a bunch of 3rd party hacks. We're can't delay any longer.

My thoughts:

- If we need another LTR in the 2.0 series (I'm not convinced we do),
the 2.14 should be this release. Followed by a 6 month cycle for 3.0
-  If not, then the 2.14 release should be 3.0 (with a 6 month cycle)

Nyall




>
> I know there has been a QEP for it start but I'm going to just start a wiki
> checklist and we can put some notes in that for now.  This is something we
> will need to move together on and make sure everyone is ready for, including
> users.
>
> Regards,
>
> On Wed, Oct 14, 2015 at 4:20 PM, Paolo Cavallini <cavallini at faunalia.it>
> wrote:
>>
>> Il 14/10/2015 08:16, Andreas Neumann ha scritto:
>> > And of course the change to QT5 / Python 3 should happen immediately
>> > after the next LTS release - to give enough time to stabilize for the
>> > LTS release after the next LTS. Given the cited problems with OSX and
>> > qt4 it makes sense to do the switch after the next LTS.
>>
>> Sure. Another option, if we feel there are no compelling reasons to have
>> another LTR (I believe 2.11 have few additional function people can't
>> really miss, and 2.8 seems generally quite well accepted), to skip next
>> LTR and go straight away with the transition after 2.12 is out.
>> The silence by our Release Manager worries me a bit ;)
>> Al the best.
>>
>> --
>> Paolo Cavallini - www.faunalia.eu
>> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
>> _______________________________________________
>> Qgis-developer mailing list
>> Qgis-developer at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer