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

Tristan Cacqueray tristan.cacqueray at enovance.com
Fri Jun 5 14:35:41 UTC 2015

On 06/05/2015 05:46 AM, 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
> user.
> What would be your preferred option ?

Apologize if I'm off-track here, but Plan A and D seems like a steep
change for users. Imo having stable release (at least between two
releases) is a valid use-case.

I guess Plan C is the preferred option, along with a "stable-release"
tag, projects that opt-in would have the responsibility to create stable
branches and maintain them.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150605/a0164aba/attachment.pgp>

More information about the OpenStack-dev mailing list