<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto">Hi,</div>
</div>
<div name="messageReplySection">
<div dir="auto">On 9 Jun 2020, 17:01 +0700, Thierry Carrez <thierry@openstack.org>, wrote:<br /></div>
<blockquote style="border-left-color: rgb(26, 188, 156); margin: 0px; padding-left: 10px; border-left-width: thin; border-left-style: solid; padding-bottom: 5px; padding-top: 5px;">instead of doing a 14.0.0.0rc1 and then a 14.0.0.0rc2 that gets promoted</blockquote>
<blockquote style="border-left-color: rgb(26, 188, 156); margin: 0px; padding-left: 10px; border-left-width: thin; border-left-style: solid; padding-bottom: 5px; padding-top: 5px;">to 14.0.0, we would produce a 14.0.0, then a 14.0.1 and just list that</blockquote>
<blockquote style="border-left-color: rgb(26, 188, 156); margin: 0px; padding-left: 10px; border-left-width: thin; border-left-style: solid; padding-bottom: 5px; padding-top: 5px;">14.0.1 in the release page at coordinated release time.</blockquote>
<div dir="auto"><br />
I like this part because to me it feels like those RCs nowadays are often<br />
not necessary to do from development perspective but still "have to" because<br />
it’s just such a release process. On the other hand, RCs are useful when the project<br />
is really being actively developed (new features, refactoring etc) because it helps<br />
to get something pretending to be the final release but there’s still a chance to<br />
update it if testing helped find some issues.<br />
For what it’s worth, I think having less versions is better, especially if all artificial<br />
(procedural if you will) ones are gone. Less confusing for users and new<br />
contributors. Such confusions really happen once in a while in practice.<br />
<br />
<br />
Thanks<br />
<br />
Renat Akhmerov<br />
@Nokia<br />
<br /></div>
</div>
</body>
</html>