Workflow with 'never commit broken changes'
John A Meinel
john at arbash-meinel.com
Tue Jun 27 00:10:54 BST 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Erik Bågfors wrote:
...
> Anyway, if you then fix a bug, you commit with "bugfix for #348",
> which will automatically close the bug in that branch, and show you
> that you need to cherrypick/merge that bugfix into the other affected
> branches to fix the problem.
>
> This requires the VCS to understand cherrypicks better than bzr does
> right now of course.
>
> But I think a bugtracker that can sit outside of branches and know
> about which branches has registered bug, would be really useful.
>
> It's very late and this all gets very confusing pretty quick :)
>
> Regards,
> Erik
>
You probably should look at Aaron Bentley's 'bugs everywhere' bug tracker.
http://www.panoramicfeedback.com/opensource/
I haven't used it myself. But he basically built it as a 'distributed
bug tracker.'
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEoGl+JdeBCYSNAAMRAjMUAJoCmZFmo5qfa/WVfDx49C/YK8fq5ACdFP5B
PjQzDLGS5WCejgXzTGaXl+g=
=1RHR
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list