have a release branch

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> 2009/2/17 Robert Collins <robertc at robertcollins.net>:
>> On Tue, 2009-02-17 at 15:07 +1100, Martin Pool wrote:
>>>> I understand Robert's idea as having an *additional* branch named
>>>> 'current' where commits will be done *only* for official
>>>> releases.
>>>>
>>>> So that bzr log -n1 will shows *only* the bzr official releases,
>>>> *excluding* release candidates and of course all intermediate
>>>> commits made on release branches (which can be seen with bzr log
>>>> -n 2 (one more use case for -n 2 mwhahaha)).
>>> I'm ok with having an additional branch containing the most current
>>> released copy.  I don't see how getting rid of the current release
>>> branches would help anything and it would make some things worse.
>> I wasn't proposing removing anything :). Just adding a convenience for
>> folk that 'want the latest release' - one such audience is packagers.
> 
> OK, I've created http://code.launchpad.net/~bzr/bzr/latest for that
> purpose.  It is not fully populated yet, because I'm going to make
> commits for every release as vila suggests.
> 
> It will be helpful for doc generation and the benchmark machine too.
> 

You can use the tags in
'http://bzr.arbash-meinel.com/branches/bzr/jam-integration'. I've tried
to create a tag for every release that I was able to track down.

Since ~1.5 I've tracked the release candidates. Also, only the revisions
since 1.1 are actually in bzr's trunk. Somewhere around there was when
we changed from "release branches never get merged back to trunk", to
"merge back to trunk after release".

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmmrooACgkQJdeBCYSNAAPxNwCfYH9Gk7e/bH5YHxMs2rVJx2fJ
rX4AoM7UyFja1Mp5py4WZU6NIByxM6+Z
=lf+W
-----END PGP SIGNATURE-----