Current details for split-inventory work
John Arbash Meinel
john at arbash-meinel.com
Wed Dec 3 15:13:57 GMT 2008
-----BEGIN PGP SIGNED MESSAGE-----
Stephen J. Turnbull wrote:
> Jari Aalto writes:
> > was 1.0 released? or 1.1? Person complaining that his bzr 1.x "does not
> > work", cannot see that his bzr is old. With date based versions it'd be
> > obvious:
> > YYYYMMDD
> The date is obvious, but whether anything important has changed, and
> how much has changed, since then is not.
> > Btw, the "rc*" naming is nightmare for automatic watching of new
> > releases. With pure "sort" naming, a bot could examine web page and send
> > mail when new release is available.
> This is what overridable methods are for. Several packages are
> available for dealing with this, including one in Python which
> specifically has code for dealing with the rcN style.
My suggestion would be to just fold the date into the version string.
You have the obvious date, and you have a number indicating "quality".
It *is* a bit verbose, but it is also obviously a date, and does satisfy
the "wow my bzr-0.7-20060109 really is old".
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar