changing revision properties

[John Arbash Meinel]

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

Aurélien Naldi wrote:
> Hi,
> 
> we have a small project using bazaar and currently setting up a bug tracker.
> I'm thus looking at their interoperability and discoverd "bzr commit
> --fixes ..." which work fine.
> 
> I also found out how to get these properties from python code which is great.
> 
> Now, I am affraid the address/configuration of our bug tracker may
> change later on and I'm willing to avoid pain when/if it happens.
> Fixed bugs are stored in the "properties" dict of a revision, I can
> change its value but the changes are not saved to the repository.
> While it sounds reasonable to prevent such changes, is it a
> (practical) way to force them to happen ?

It is not very safe to change any data that is stored in the repository,
because that data has likely propagated to other repositories already.
(Your local copy, my branch of your work, etc.)

> 
> I don't know if it is relevant but we are not (yet) signing commits.
> 
> Best regards
> 

So I would say that in the mid-term, whatever work you are doing to
extract the urls for fixes, can just be updated to have a possible
mapping. So that "http://foo/bug_id" can be mapped to
"http://bar/bug_id" if your website changes. Changing websites doesn't
happen often, and the original URL is unlikely to ever collide. (I don't
think you will later bring up a different bug tracker at the old
location that now has some of the bugs but not all of them, etc.)

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

iEYEARECAAYFAknKQ2QACgkQJdeBCYSNAANIQQCaAuvrgMZ/PX+LQJqc0y32GN7l
KpgAn0V8ATuP7TCT+ACWT9E9I0klt/Nm
=bL9V
-----END PGP SIGNATURE-----