[Development] Qt 5.10 schedule proposal

[Aleix Pol]

On Thu, Apr 13, 2017 at 1:48 PM, Jani Heikkinen <jani.heikkinen at qt.io> wrote:
> After short internal discussion here is my proposal for those patch level releases:
>
>     - Branch '5.6.3' from '5.6' at the end of May/beginning of June, 5.6.3 release target August 2017
>     - Branch '5.9.1' from '5.9' at the end of July/beginning of August, 5.9.1 release target September 2017
>     - Branch '5.9.2' from '5.9' Nov 2017
>     - Branch '5.6.4' from '5.6' Jan 2018
>
> br,
> Jani
>
>
>> -----Original Message-----
>> From: Development [mailto:development-bounces+jani.heikkinen=qt.io at qt-
>> project.org] On Behalf Of Thiago Macieira
>> Sent: maanantaina 10. huhtikuuta 2017 18.46
>> To: development at qt-project.org; releasing at qt-project.org
>> Subject: Re: [Development] Qt 5.10 schedule proposal
>>
>> Em segunda-feira, 10 de abril de 2017, às 00:39:09 PDT, Jani Heikkinen
>> escreveu:
>> > Hi,
>> >
>> > Qt 5.9 is proceeding quite well and it is time to start planning Qt
>> > 5.10 schedule. We want to to release 5.10 before Christmas so we need
>> > to have Qt
>> > 5.10 FF at the beginning of August. I propose following initial
>> > schedule for Qt 5.10:
>> >
>> > - Qt 5.10 Feature Freeze: 8.8.2017
>> > - Qt 5.10 Alpha Release: 31.8.2017
>> > - First Qt 5.10 Beta Release 5.10.2017
>> > - Qt 5.10 RC 16.11.2017
>> > - Qt 5.10 final release 30.11.2017
>>
>> Can you add the Qt 5.6.3, 5.6.4 and 5.9.1 relase dates to the list, so we have
>> an idea of how much work it will be?

On another thread it was discussed as per assumption that the stable
branch (i.e. 5.9 in this case) can always be used. Would it be
feasible to shorten minor release periods? People will end up using it
anyway and the Qt project better make it easy to use a controlled
version rather than a random HEAD from the stable branch.

Furthermore, I don't think it's enough to wait 3 months to get a
stable release, we want people to have an incentive to submit upstream
and fix stuff in Qt rather than adding workarounds in their solutions.

Aleix