[openstack-dev] [all] [stable] No longer doing stable point releases
zigo at debian.org
Wed Jun 10 08:53:46 UTC 2015
On 06/05/2015 02:46 PM, Thierry Carrez wrote:
> So.. summarizing the various options again:
> Plan A
> Just drop stable point releases.
> (-) No more release notes
> (-) Lack of reference points to compare installations
> Plan B
> Push date-based tags across supported projects from time to time.
> (-) Encourages to continue using same version across the board
> (-) Almost as much work as making proper releases
> Plan C
> Let projects randomly tag point releases whenever
> (-) Still a bit costly in terms of herding cats
> Plan D
> Drop stable point releases, publish per-commit tarballs
> (-) Requires some infra changes, takes some storage space
> Plans B, C and D also require some release note / changelog generation
> from data maintained *within* the repository.
> Personally I think the objections raised against plan A are valid. I
> like plan D, since it's more like releasing every commit than "not
> releasing anymore". I think it's the most honest trade-off. I could go
> with plan C, but I think it's added work for no additional value to the
> What would be your preferred option ?
I see no point of doing D. I already don't use tarballs, and those who
do could as well switch to generating them (how hard is it to run
"python setup.py sdist" or "git archive"?).
What counts is having a schedule date, where all distros are releasing a
point release, so we have a common reference point. If that is a fully
automated process, then great, less work for everyone, and it wont
change anything from what we had in the past (we can even collectively
decide for point release dates...).
Thomas Goirand (zigo)
More information about the OpenStack-dev