[openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

Ian Cordasco sigmavirus24 at gmail.com
Tue Mar 22 21:39:02 UTC 2016


 

-----Original Message-----
From: Alan Pevec <apevec at gmail.com>
Reply: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Date: March 22, 2016 at 14:21:47
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Subject:  Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

> > The release team discussed this at the summit and agreed that it didn't really matter.  
> The only folks seeing the auto-generated versions are those doing CD from git, and they  
> should not be mixing different branches of a project in a given environment. So I don't  
> think it is strictly necessary to raise the major version, or give pbr the hint to do so.  
>  
> ok, I'll send confused RDO trunk users here :)
> That means until first Newton milestone tag is pushed, master will
> have misleading version. Newton schedule is not defined yet but 1st
> milestone is normally 1 month after Summit, and 2 months from now is
> rather large window.

This affects other OpenStack projects like the OpenStack Ansible project which builds from trunk and does periodic upgrades from the latest stable branch to whatever is running on master. Further they're using pip and this will absolutely cause headaches upgrading that.
--  
Ian Cordasco




More information about the OpenStack-dev mailing list