have a release branch

[Robert Collins]

I'd like to change/add to how we do releases the idea of having a
'current' branch of bzr.dev, which is always the current release.

Basically just 'bzr push 1.12 current' now, and then after each full
release (not beta etc) either push to current again (tags letting us get
at older releases there), or merge to current (left hand history in
current is each release).

I think merge to current is probably most useful.

This would make packaging a 'current release' of bzr a little easier, I
think, because the branch URL wouldn't be changing.

-Rob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090213/bc931f37/attachment.pgp