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

Renat Akhmerov renat.akhmerov at gmail.com
Tue Jun 9 11:32:04 UTC 2020

On 9 Jun 2020, 17:01 +0700, Thierry Carrez <thierry at openstack.org>, wrote:
> 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 like this part because to me it feels like those RCs nowadays are often
not necessary to do from development perspective but still "have to" because
it’s just such a release process. On the other hand, RCs are useful when the project
is really being actively developed (new features, refactoring etc) because it helps
to get something pretending to be the final release but there’s still a chance to
update it if testing helped find some issues.
For what it’s worth, I think having less versions is better, especially if all artificial
(procedural if you will) ones are gone. Less confusing for users and new
contributors. Such confusions really happen once in a while in practice.


Renat Akhmerov

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200609/11538742/attachment.html>

More information about the openstack-discuss mailing list