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

Kuvaja, Erno kuvaja at hp.com
Mon Jun 8 11:55:01 UTC 2015

> -----Original Message-----
> From: Thierry Carrez [mailto:thierry at openstack.org]
> Sent: Friday, June 05, 2015 1:46 PM
> To: openstack-dev at lists.openstack.org
> Subject: Re: [openstack-dev] [all] [stable] No longer doing stable point
> releases
> 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 user.
> What would be your preferred option ?
> --
> Thierry Carrez (ttx)

I don't think plans B & C are any benefit for  anyone based on the statements discussed earlier so won't be repeating those. One thing I like about plan D is that it would give also indicator how much the stable branch has moved in each individual project. 

Yes this can be seen from git, but also having just running number on the stable release for each commit would be really quick glimpse opposed to SHAs or counting  the changes from git  log.

- Erno

More information about the OpenStack-dev mailing list