Open Stack

2016-02-26 19:51 GMT+01:00 Robert Collins <robertc at robertcollins.net>:
> On 27 February 2016 at 00:13, Neil Jerram <Neil.Jerram at metaswitch.com> 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
>> for me, and output:
>
> pbr does that automatically, generating a pre-release version. The
> regular part of the version is the lowest version number you can use
> that will match the semver rules.

So to help PBR, all projects should be inserting commit with Sem-Ver:
api-break after stable/mitaka was cut, without that we have the same
major version on both branches e.g. nova:

$ git checkout master
$ python ./setup.py --version
13.0.0.0rc2.dev48

$ git checkout stable/mitaka
$ python ./setup.py --version
13.0.0.0rc2.dev10

After pushing empty commit to the master with the message like:
    Newton bump major version

    Sem-Ver: api-break
    Change-Id: I8a2270d5a0f45342fe418b3018f31e6ef054fe9e

$ python ./setup.py --version
14.0.0.dev49

Any reason not to do that? Other option is to push alpha tag to
master, but that would be weird IMHO.


Cheers,
Alan