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

On 2016-03-25 09:14:27 -0400 (-0400), Doug Hellmann wrote: > OK. It looks like it grabs the tagged commit from the stable branch > and merges that back into master, expecting the results to be null > because we backport all changes to stable branches and don't introduce > anything new there. Is

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 Jeremy Stanley's message of 2016-03-25 12:50:04 +: > On 2016-03-25 08:41:51 -0400 (-0400), Doug Hellmann wrote: > > All of our projects are able to tag releases in master *and* stable > > branches. We regularly release stable updates to libraries. > > > > I'm embarrassed to say

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

On 2016-03-25 08:41:51 -0400 (-0400), Doug Hellmann wrote: > All of our projects are able to tag releases in master *and* stable > branches. We regularly release stable updates to libraries. > > I'm embarrassed to say I don't know what the job you describe about > merging tags into master does.

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 David Moreau Simard's message of 2016-03-24 16:56:55 -0400: > On Thu, Mar 24, 2016 at 1:58 PM, Doug Hellmann wrote: > > Let's turn the question around: Why do you (or anyone) want to > > package things that are not tagged as releasable by the contributors > >

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 Jeremy Stanley's message of 2016-03-24 21:30:34 +: > On 2016-03-24 16:21:30 -0500 (-0500), Ian Cordasco wrote: > > Also this only affects libraries and not the server projects. > > Besides, hasn't this community always asserted that no one > > installs from PyPI anyway (inspite

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

On 2016-03-25 10:39:12 +1300 (+1300), Robert Collins wrote: > On 25 March 2016 at 10:30, Jeremy Stanley wrote: > > On 2016-03-24 16:21:30 -0500 (-0500), Ian Cordasco wrote: > >> Also this only affects libraries and not the server projects. > >> Besides, hasn't this community

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

On 25 March 2016 at 10:30, Jeremy Stanley wrote: > On 2016-03-24 16:21:30 -0500 (-0500), Ian Cordasco wrote: >> Also this only affects libraries and not the server projects. >> Besides, hasn't this community always asserted that no one >> installs from PyPI anyway (inspite of

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

On 2016-03-24 16:21:30 -0500 (-0500), Ian Cordasco wrote: > Also this only affects libraries and not the server projects. > Besides, hasn't this community always asserted that no one > installs from PyPI anyway (inspite of evidence of projects > allowing just that based on user feedback)? The

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

t;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? > On 2016-03-25 08:28:16 +1300 (+1300), Robert Collins wrote: > > However, Doug and I just uncovered a

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

On 2016-03-25 08:28:16 +1300 (+1300), Robert Collins wrote: > However, Doug and I just uncovered a concern on IRC: having PyPI be > ahead of master for more than very short periods seems like a poor > idea. > > When we tag a final release on a branch, without master being higher > than that final

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

On Thu, Mar 24, 2016 at 1:58 PM, Doug Hellmann wrote: > Let's turn the question around: Why do you (or anyone) want to > package things that are not tagged as releasable by the contributors > creating them? What are those packages used for? I know Ubuntu provides similar

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

On 25 March 2016 at 08:23, Ian Cordasco wrote: > > Right I'm not convinced it's more than the ~15 or 20 of us that work on OSA > and care about upgrading and catching regressions early. However, Doug and I just uncovered a concern on IRC: having PyPI be ahead of master

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

On 25 March 2016 at 07:25, Chris Dent wrote: > On Thu, 24 Mar 2016, Doug Hellmann wrote: > > [good explanation snipped] > > Thanks for the detailed explanation. > > As with so many of these bits of automation they come with a variety > of compromises. After a while it

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

t;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? > On 24 March 2016 at 10:36, Ian Cordasco wrote: > > > > > > > The project will bui

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

On 25 March 2016 at 01:11, Alan Pevec wrote: > 2016-03-24 2:21 GMT+01:00 Robert Collins : >> Trunk will rapidly exceed mitaka's versions, leading to no confusion too. > > That's the case now, RC1 tags are reachable from both branches and > master has

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 Chris Dent's message of 2016-03-24 18:25:10 +: > On Thu, 24 Mar 2016, Doug Hellmann wrote: > > [good explanation snipped] > > Thanks for the detailed explanation. > > As with so many of these bits of automation they come with a variety > of compromises. After a while it starts

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

On Thu, 24 Mar 2016, Doug Hellmann wrote: [good explanation snipped] Thanks for the detailed explanation. As with so many of these bits of automation they come with a variety of compromises. After a while it starts to seem like maintaining those compromises becomes as important as solving the

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 Chris Dent's message of 2016-03-24 17:25:33 +: > On Thu, 24 Mar 2016, Alan Pevec wrote: > > > Another example (not release:managed project but still) where we have > > this confusion is gnocchi: > > openstack/gnocchi > master $ python ./setup.py --version > > 2.0.1.dev61 > >

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 Alan Pevec's message of 2016-03-24 17:06:54 +0100: > > So, if Delorean includes packages built from untagged commits in > > Nit clarification: let's call it RDO Trunk repository (Delorean is a > tool, recently renamed https://github.com/openstack-packages/dlrn ) OK. > > >

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

On Thu, 24 Mar 2016, Alan Pevec wrote: Another example (not release:managed project but still) where we have this confusion is gnocchi: openstack/gnocchi > master $ python ./setup.py --version 2.0.1.dev61 openstack/gnocchi > stable/2.0 $ python ./setup.py --version 2.0.3.dev13 Sorry, I've

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

> So, if Delorean includes packages built from untagged commits in Nit clarification: let's call it RDO Trunk repository (Delorean is a tool, recently renamed https://github.com/openstack-packages/dlrn ) > multiple branches, placed in the same package repository where an > automated installation

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 Ihar Hrachyshka's message of 2016-03-24 08:44:35 +0100: > Doug Hellmann wrote: > > > Excerpts from Alan Pevec's message of 2016-03-22 20:19:44 +0100: > >>> The release team discussed this at the summit and agreed that it didn't > >>> really matter. The only

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

2016-03-24 2:21 GMT+01:00 Robert Collins : > Trunk will rapidly exceed mitaka's versions, leading to no confusion too. That's the case now, RC1 tags are reachable from both branches and master has more patches, generating higher .devN part. But once RC2 and final tags

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

Doug Hellmann wrote: Excerpts from Alan Pevec's message of 2016-03-22 20:19:44 +0100: 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

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

On 24 March 2016 at 13:23, Dean Troyer wrote: > On Wed, Mar 23, 2016 at 3:03 PM, Doug Hellmann > wrote: >> >> Are you packaging unreleased things in RDO? Because those are the only >> things that will have similar version numbers. We ensure that whatever

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

On 24 March 2016 at 10:36, Ian Cordasco wrote: > > > 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

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

On Wed, Mar 23, 2016 at 3:03 PM, Doug Hellmann wrote: > Are you packaging unreleased things in RDO? Because those are the only > things that will have similar version numbers. We ensure that whatever > is actually tagged have good, non-overlapping, versions. > The

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

> > 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 > > afte

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 Alan Pevec's message of 2016-03-22 20:19:44 +0100: > > 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

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

Date: March 22, 2016 at 14:21:47 > To: OpenStack Development Mailing List (not for usage questions) > <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 prio

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

t;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? > > The release team discussed this at the summit and agreed that it didn't > > really matter. > The onl

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

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

> On Mar 22, 2016, at 2:10 PM, Alan Pevec wrote: > > 2016-02-26 19:51 GMT+01:00 Robert Collins : >>> On 27 February 2016 at 00:13, Neil Jerram >>> wrote: >>> I understand the semantic versioning algorithm for

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

2016-02-26 19:51 GMT+01:00 Robert Collins : > On 27 February 2016 at 00:13, Neil Jerram wrote: >> I understand the semantic versioning algorithm for calculating a new >> version. But what do I run, in a git repository, to do that calculation