[Development] Proposal to adjust release candidate process

Marco Bubke Marco.Bubke at qt.io
Wed Dec 21 16:20:50 CET 2016

I think many users see a beta as something you better not touch, but a release candidates can be trusted much more. I know it's not intended that way but people learned by experiences. [?]

Maybe "pre release" or "preview" could be a name to show the final status?

From: Development <development-bounces+marco.bubke=qt.io at qt-project.org> on behalf of Thiago Macieira <thiago.macieira at intel.com>
Sent: Wednesday, December 21, 2016 3:45:37 PM
To: development at qt-project.org
Subject: Re: [Development] Proposal to adjust release candidate process

Em ter?a-feira, 20 de dezembro de 2016, ?s 13:34:39 BRST, Tuukka Turunen
> If desired, we could use some other name than "Release Candidate 1" for the
> release that begins the last phase of the release. It could be called "Beta
> 2" or "Technology preview", if so desired. Personally, I would call it
> "Release Candidate 1".
> The difference to our current process is quite small. In essence it would be
> about considering the "RC1" the beginning of the final releasing phase (.0
> branch), not something we do almost at the end of it. I believe that
> lowering the quality criterial for "RC1" helps us in being more efficient
> as it has been in practice impossible to really fulfill the current process
> goal and have already the first RC as good as the final.

I like the process, but I would also rename the release like you proposed. We
can't have something called "release candidate" when we *know* it's not a
candidate. Let's call it beta 2, beta 3, etc. until we can make it a release.

Release candidates are really the snapshots that the release team creates when
we're testing for sanity right before the actual release.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

Development mailing list
Development at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20161221/21da8e9e/attachment.html>

More information about the Development mailing list