[openstack-dev] [all] [stable] No longer doing stable point releases

Alan Pevec apevec at gmail.com
Sun Jun 7 22:46:57 UTC 2015

> How do you check if project X in version n works with project Y in
> version m, using this non-scheduled point release "free for all" model?

That was an illusion of point releases, as Thierry said there wasn't
significantly more testing and I don't remember any testing reports
during stable freeze periods.
All we had was upstream CI testing, but that's what we get for every commit.

> Why every 2 weeks? Why every month?

Sure, no problem, every distro can update whenever it works for them,
what is important for me is that we have a common reference points.
With plan D that would be automatically generated maj.min.N where N is
the number of commits since maj.min tag which doesn't depend on
anyone's manually pushing git tag.

> Not synchronizing brings a bunch of problems. The only problem raised by
> synchronous point releases is "we don't have enough resources", which I
> fail to understand, given how cheap it is to tag a release. If the
> release managers don't have enough time to do so, it is my view that
> it's ok to give this power to individual projects. But that's orthogonal
> to having synchronous point releases.

Tag is indeed cheap, this is more about reflecting reality and not
keeping this "synchronized" illusion alive.
BTW point release process is more[1] than just pushing signed git tag,
the most time consuming work is cats herding (i.e. pushing for reviews
before the freeze) and Launchpad pruning.
The former was hopeless and will be even more with big-tent and the
latter we should avoid by automatically generated changelog.


[1] https://wiki.openstack.org/wiki/StableBranchRelease

More information about the OpenStack-dev mailing list