[all][release] One following-cycle release model to bind them all

Jeremy Stanley fungi at yuggoth.org
Tue Jun 9 17:39:58 UTC 2020

On 2020-06-09 12:00:14 +0200 (+0200), Thierry Carrez wrote:
> In the "follows-cycle" model, deliverables would be released at least once
> per cycle, but could be released more often. The "final" release would be
> marked by creating a release (stable) branch, and that would need to be done
> before a deadline. Like today, that deadline depends on whether that
> deliverable is a library, a client library, a release-trailing exception or
> just a regular part of the common release.
> The main change this proposal introduces would be to stop having release
> candidates at the end of the cycle. Instead we would produce a release,
> which would be a candidate for inclusion in the coordinated OpenStack
> release. New releases could be pushed to the release branch to include late
> bugfixes or translation updates, until final release date. So instead of
> doing a and then a that gets promoted to 14.0.0, we
> would produce a 14.0.0, then a 14.0.1 and just list that 14.0.1 in the
> release page at coordinated release time.

I suppose this will also have the effect that the official release
tags will now appear in the history of the master branch. That will
be nice.
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200609/451cc2bb/attachment.sig>

More information about the openstack-discuss mailing list