[RFC] including revision ids/revnos in releases
John Arbash Meinel
john at arbash-meinel.com
Thu Jul 17 21:07:44 BST 2008
-----BEGIN PGP SIGNED MESSAGE-----
One thing I'd like to add to the release process, is somehow embedding
the revision id into the release. This could be a simple as just doing
"bzr version-info --format=python > bzrlib/_version_info.py". Though we
also need to hook up the other code so that it gets printed by 'bzr
- --version'. We already will open a containing branch, the idea is to
just get that same information into the release.
The biggest reason why I'm thinking of it now, is because I want to put
together an installer for win32, which matches the exact revision that
Martin put into the PPA.
However, it wasn't tagged, and we didn't create a 1.6 branch (because it
is only a beta release.) For now, I'll just grab the tarball, but it
would be nice if that information was available at runtime.
-----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