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 YYYY.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 :) 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. Bonus points for calling a version function from setup.py to avoid such issues in the future. -- 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