tortoisebzr-developers team mailing list archive
-
tortoisebzr-developers team
-
Mailing list archive
-
Message #00040
Release numbering
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
So we're trying to get the Windows installer to be build using the zope
buildout tools. Mostly because it means it will be easier to set up a
buildbot to automatically build the installer.
Anyway, in doing this, it is nice to have a tag to release from. Right
now, there is only 1 tag:
release-0.1.0 124
I've been building the installer from whatever is the latest tip.
I'm wondering if we want to:
1) Use a number which matches the released bzr that goes with it. This
is a bit tricky as they won't really release "in sync". I would expect
us to use the same tbzr between releases. Unless we specifically just
update a version number in order to release a "matching" version.
2) Just pick the next number, like "0.2.0" and let whoever does a
commit decide whether this needs to be a major/minor update.
Thoughts?
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkpzXbkACgkQJdeBCYSNAAMZKwCgh8tie5kTMAf11kbN3nfkgbdT
u18An2+zWxbgRjYy3fsB4EtaYhEkJwqr
=hIOz
-----END PGP SIGNATURE-----