[Development] Qt 5.12 schedule proposal & proposal for release process change

Jani Heikkinen jani.heikkinen at qt.io
Tue Apr 17 11:40:10 CEST 2018

> -----Original Message-----
> From: Edward Welbourne
> Sent: tiistai 17. huhtikuuta 2018 12.09
> To: Jani Heikkinen <jani.heikkinen at qt.io>; Alex Blasche
> <alexander.blasche at qt.io>
> Cc: Qt development mailing list <development at qt-project.org>
> Subject: Re: [Development] Qt 5.12 schedule proposal & proposal for release
> process change
> To paraphrase and possibly mangle Jani's plan (without opinion on whether I
> like it; this is about making sure I understand the plan):
> Summary:
> * Make snapshots and FF, not release, the time-based part of our process.
> Details:
> * Make snap-shots regularly, merely changing their naming as we move
>   through the phases below.
> * Branch, release first alpha and start API review at FF.  Ever step
>   after this takes as long as it does; and we try to keep each short.
> * Name snap-shots alpha n; all API changes must be notified to the
>   review for their module, prompting an update to that review.
> * When API review is complete and all features are completely
>   implemented, transition to beta.  Only bug-fixes come in after this.
> * Name snap-shots beta n after this; ask folk to test beta 1 and report
>   bugs; triage bugs, fix blockers.
> * When the blocker list is empty, transition to RC.  If we can't find
>   any "brown paper bag" issues, ship it; otherwise, fix, rinse and
>   repeat.
> Jani: how far have I mangled your intent in expressing it thus ?
> 	Eddy.

This is exactly what I meant.


More information about the Development mailing list