[Development] Proposal to adjust release candidate process
tuukka.turunen at qt.io
Fri Dec 23 08:17:01 CET 2016
> -----Original Message-----
> From: Development [mailto:development-
> bounces+tuukka.turunen=qt.io at qt-project.org] On Behalf Of Thiago
> Sent: torstaina 22. joulukuuta 2016 22.09
> To: development at qt-project.org
> Subject: Re: [Development] Proposal to adjust release candidate process
> Em quinta-feira, 22 de dezembro de 2016, às 12:54:08 BRST, Tuukka Turunen
> > > And besides, alpha and beta are traditional and well understood.
> > > (Following that pattern though, I guess we ought to call the RC a
> > > “gamma”, but that’s not traditional for some reason.)
> > If we do not want to call the first development release from the
> > release branch "Release Candidate 1", then I think calling it "Release
> > Preview" is a good approach.
> Call it beta 2 (or gamma 1) right after branch and one we've iterated and we
> could have released, we call it release candidate. We release them more
> often, with more iterations, so that we get more feedback. I think that's the
> most important part.
Beta 2 is still a bit misleading in my opinion. It is coming from release branch, so we are beyond the Beta phase. Let's think about the name later, after the holidays. It anyway seems that the basic approach is seen viable.
I would like to try this with Qt 5.9. The current scheduling lists the RC for 17th of May. What would then be the anticipated time to release the gamma/beta2/preview release as soon as we are in the 5.9.0 branch? Perhaps around 3rd of May?
> Thiago Macieira - thiago.macieira (AT) intel.com
> Software Architect - Intel Open Source Technology Center
> Development mailing list
> Development at qt-project.org
More information about the Development