-----Original Message----- From: Doug Hellmann <d...@doughellmann.com> Reply: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Date: March 23, 2016 at 15:04:15 To: openstack-dev <openstack-dev@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?
> Excerpts from Ian Cordasco's message of 2016-03-22 16:39:02 -0500: > > > > > > -----Original Message----- > > From: Alan Pevec > > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: March 22, 2016 at 14:21:47 > > To: OpenStack Development Mailing List (not for usage questions) > > 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. > > Are you saying the Ansible playbooks install server projects using pip? > For that to be a problem they would have to be installing from git URLs > or directly from tarballs. Is that the case? The project will build wheels first. The wheels generated tend to look something like 13.0.0.0rc2.dev10 when they're built because of pbr. If someone is doing CD with the openstack-ansible project and they deploy mitaka once it has a final tag, then they decide to upgrade to run master, they could run into problems upgrading. That said, I think my team is the only team doing this. (Or at least, none of the other active members of the IRC channel talk about doing this.) So it might not be anything more than a "nice to have" especially since no one else from the project has chimed in. -- Ian Cordasco __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
