Problem with mutability of "official" branch

[Aaron Bentley]

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

Doug Lee wrote:
> In what I think is a typical structure where there's an "official"
> branch from which releases are made, is there a way to avoid the
> following two problems, biggest first?  The commands below are done
> from a checkout of the "official" branch:
> 
> 1.  "bzr push --overwrite" wiping out a revision that was released,
> whether or not it was tagged.
> 
> 2.  "bzr merge" and then "bzr push" changing the revision number
> of an already-released revision (a tag would still get to it, but
> if there's no tag and people try using the revision number, it won't
> be the same revision anymore!).

You can set "append_revisions_only" on the branch.  See "bzr help
configuration".

e.g., you could do "echo append_revisions_only=true >>
.bzr/branch/branch.conf"

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFI1WlK0F+nu1YWqI0RAnMfAJ463890fmvTZsFwNuvCNlg9YuDJHQCfbNzh
LqfY+HdniT/Kh3stXkGZ1A8=
=UYsn
-----END PGP SIGNATURE-----