EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Bazaar commit messages: style guide
From: Ralph Lange <[email protected]>
To: [email protected]
Date: Wed, 18 Aug 2010 15:16:50 -0400
 On 18.08.2010 14:15, Andrew Johnson wrote:
I would prefer that if possible we use the Bazaar --fixes option for recording
that a commit fixes a known bug, since Launchpad will pick up on that
automatically.

I tried that with my commit 12094 seven days ago, closing bug  lp:615916.

Fact is, Bazaar records that information (including a bug tracker URL to the issue) in the patch:
The branch browser shows a link to the bug.
"bzr qlog" shows the bug has been fixed and a link in the meta-info box, and puts colored tags to revisions. I did not find a way to grep the output of "bzr log" for a bug number unless it is in the commit message.

Launchpad did pick up much:
It does not update the bug status in any way, so the bug's status is still "In Progress", not "Fix Committed".
It does not add a link to the revision to the bug report.
(Launchpad claims to add a link from the bug page to the branch page and vice versa, though. In this case I was adding that relation when I created the bug report.)

   I'm not going to object to people adding this kind of
information as well if they like, but I don't want to make it a rule that we
have to enforce.

That's fine, as Bazaar seems to correctly add and show the link to the closed bug, and Launchpad probably does create links between the bug and the branch that fixes it.

There is no way to create a bug relation other than "fixed" on a commit. "Is related to" has to be done manually through email or web interface.

And you still have to edit and close the bug manually. That is actually quite disappointing, since other systems (Trac, Redmine, ...) integrate the bug tracker in a way that lets you actually close bugs by commit message.

I have added these suggestions to the new Wiki page at
http://www.aps.anl.gov/epics/wiki/index.php/Style_Guide_for_Bazaar_commit_messages

Thanks a lot!
Ralph


Replies:
Re: Bazaar commit messages: style guide Andrew Johnson
References:
Bazaar commit messages: style guide Andrew Johnson
Re: Bazaar commit messages: style guide Ralph Lange
Re: Bazaar commit messages: style guide Andrew Johnson

Navigate by Date:
Prev: Re: Bazaar commit messages: style guide Andrew Johnson
Next: Re: Bazaar commit messages: style guide Andrew Johnson
Index: 2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Bazaar commit messages: style guide Andrew Johnson
Next: Re: Bazaar commit messages: style guide Andrew Johnson
Index: 2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·