[RFC] commit --fixes xxx: please, store actual bug id in addition to full URL

[Nicholas Allen]

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

That makes more sense to me. It would be better if only the bug id was
stored and there was another property on the branch as a whole (not on a
revision) that defined the URL for bugs in general.

Then you just need --fixes=bug_number instead of --fixes=lp:bug_number
etc. It's unlikely that a single branch will use more than one bug
tracker. This is much better because the URL for the bug tracker may
change over time, or the project might migrate from one bug tracker to
another. If just the bug IDs are stored then this is no problem - you
just update the branch's bug tracker location.

Cheers,

Nick

Alexander Belchenko wrote:
> It's not quite rfc, just as the question I'd like to make bzr.devs aware
> of.
> 
> Currently bzr commit --fixes=xxx store full URL to the bug page.
> 
> In QBzr we're using special regex to extract bug id back to original
> form and then represent them in qlog view as "bug #12345".
> (For example see http://qbzr.googlegroups.com/web/qlog.png)
> 
> To support every new bug tracker we have to add specialized regex
> to parse full URL.
> 
> Maybe it makes more sense to store not only full URL to bug page (as
> today) but in addition and original bug id? So it will be much
> easier to extract this info?
> 
> 
> 

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

iEYEARECAAYFAkmmbtsACgkQ1+i51gqqEGlyHwCfQuMddfMJalbjsKxy0fpdle0Y
iq0An2UUSGs11AvdS5H8bDEeQ2ndr7iQ
=h8FF
-----END PGP SIGNATURE-----