Re: [Openstack] Keystone's stable/diablo branch

2011-11-14 Thread Mark McLoughlin
On Mon, 2011-11-14 at 10:22 +0100, Thierry Carrez wrote:
 Mark McLoughlin wrote:
  We still have a problem with versioning, though.
  
- Essex keystone will be 2012.1
  
- Diablo keystone was tagged as 2011.3
  
- Diablo keystone was actually versioned as 1.0 (see setup.py) even 
  though version() returns 0.9
  
- stable/diablo is now versioned as 0.9.1 - i.e. behind the diablo 
  version number!
  
  I think we should just adopt the .N versioning on stable/diablo, but
  this will be the first time we've released from a stable branch. How
  does 2011.3.1 sound?
 
 Good catch, I only looked into __init__.py :)
 
 I guess we can do do 1.0.1 or 2011.3.1. I prefer 1.0.1, since
 Diablo keystone was versioned 1.0. 2011.3 is actually an OpenStack
 version number, at this point if we could keep such versioning for the
 official common OpenStack releases... If it's too confusing the 2011.3
 tag could be renamed :)

Well, when I asked before whether the 1.0 version in setup.py or the
2011.3 tag was the correct version, I understood that it was the latter:

  http://www.mail-archive.com/openstack@lists.launchpad.net/msg04967.html

and so Fedora used the 2011.3 version for packaging diablo keystone.

You seem to be suggesting that incubating projects should follow a
different versioning scheme until they are accepted? I'd much rather see
incubating projects show that they can align themselves with the other
projects, rather than have them do something different.

 So I would realign both __init__.py and setup.py with a 1.0.1 that is
 superior to the 0.9 and 1.0 that were apparent in the Diablo release.

But not superior to 2011.3 which was also apparent :)

 Bonus points for calling a version function from setup.py to avoid such
 issues in the future.

That has since been added.

Cheers,
Mark.


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Keystone's stable/diablo branch

2011-11-14 Thread Thierry Carrez
Mark McLoughlin wrote:
 You seem to be suggesting that incubating projects should follow a
 different versioning scheme until they are accepted? I'd much rather see
 incubating projects show that they can align themselves with the other
 projects, rather than have them do something different.

That's the limits of common versioning... It's just that 2011.3
happens to be the OpenStack version number as well as the components
version number. So OpenStack 2011.3 implies Nova 2011.3 but Keystone
2011.3.1 doesn't imply OpenStack 2011.3.1. I'd have preferred to stay
out of that can of worm from the time being, but...

 So I would realign both __init__.py and setup.py with a 1.0.1 that is
 superior to the 0.9 and 1.0 that were apparent in the Diablo release.
 
 But not superior to 2011.3 which was also apparent :)

If 2011.3 ever was apparent, I'm OK with 2011.3.1.

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Keystone's stable/diablo branch

2011-11-13 Thread Mark McLoughlin
Hi Dolph,

On Fri, 2011-11-11 at 13:58 -0600, Dolph Mathews wrote:
 Keystone needs your help testing!
 
 The goal of this branch is to be completely compatible with diablo,
 while including as many improvements as possible. Pending your
 satisfaction, we'd like to tag this branch in the coming days.

Awesome!

We still have a problem with versioning, though.

  - Essex keystone will be 2012.1

  - Diablo keystone was tagged as 2011.3

  - Diablo keystone was actually versioned as 1.0 (see setup.py) even 
though version() returns 0.9

  - stable/diablo is now versioned as 0.9.1 - i.e. behind the diablo 
version number!

I think we should just adopt the .N versioning on stable/diablo, but
this will be the first time we've released from a stable branch. How
does 2011.3.1 sound?

(Thanks to Alan cc-ed for noticing this)

Cheers,
Mark.


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp