changing revision properties

[Aurélien Naldi]

On Wed, Mar 25, 2009 at 3:44 PM, John Arbash Meinel
<john at arbash-meinel.com> wrote:
> -----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.)

Thanks for your reply,

I do understand why this is wrong, but I'm still willing to try as I
have for now access to all branches.
My (hopefully temporary) usecase is that development and bug tracker
are internal for now (local network, without public domain name).
Thus website migration will happen and url redirection won't be possible...
If we can start putting local addresses that can be updated before we
start putting public bzr branches it is great, otherwise we will just
wait a bit longer or accept to get not-so-good-looking metadata.


Regards.

-- 
Aurélien Naldi