I noticed Dan started using a very clean format for the checkin comments as well
as noting the svn revision when changing bug reports to fixed. To add to this,
it appears that ViewCVS and bugzilla are able to make automatic links. These
are a HUGE help when tracing through changes, tracing regressions or, better
yet, avoiding them.
How this seems to work is this:
1) When committing to svn, writing comments in the form of:
will transform the first line into a link from viewCVS to the bugzilla bug
number. Use N/A if its an svn commit without a bug. This will probably make
things a lot easier for Dan as well when he has to compile the changelogs from
all the svn logs.
2) After committing to svn, a comment can then be placed in bugzilla when
marking as fixed or simply to ask for confirmations. Including the svn change
number, written out as 'change xxxx' where xxx is the change number will create
a link to the entire change in viewcvs. It is SO nice to be able to go back and
forth via these links, especially if you missed the checkins email.
Since we all have to sleep sometime, this is likely to really help in
keeping track of all that goes on as more and more capable people are working 24
hours a day improving slimserver. I think it also helps to slice through the
increasing volume of user comments to get to the code affected. As SlimDevices
actively encourages users to file bugs and enhancements, any method available
to support active user interaction while providing the option to cut through
all that to the code means the best of both worlds.
If I've missed any other bits, hopefully Dan will kick in some corrections. I
have just been observing this stuff over the last couple weeks, and I'm sure
there is more to come. I know from my own experience that I started
contributing becuase I wanted things to work the way I wanted. Admittedly,
everyone has their favourite aspects and their own priorities. But beyond
that, we're all doing this becuase SlimServer is a great product, created by
great people. If we can all do think about using the above formats as often as
possible, it makes it easier for the other guy/gal to work on their favourite
part after you have fixed your own.
thanks for your patience, you may now return to your regular pastime
Results 1 to 2 of 2
Thread: svn comments and bugzilla
2005-04-19, 22:01 #1
svn comments and bugzilla
2005-04-20, 06:04 #2Marc ShermanGuest
svn comments and bugzilla
> I noticed Dan started using a very clean format for the checkin comments as well
> as noting the svn revision when changing bug reports to fixed. To add to this,
> it appears that ViewCVS and bugzilla are able to make automatic links. These
> are a HUGE help when tracing through changes, tracing regressions or, better
> yet, avoiding them.
> How this seems to work is this:
> 1) When committing to svn, writing comments in the form of:
> Bug: xxxx
> Description: xxxx...
> will transform the first line into a link from viewCVS to the bugzilla bug
> number. Use N/A if its an svn commit without a bug. This will probably make
> things a lot easier for Dan as well when he has to compile the changelogs from
> all the svn logs.
There are scripts out there that can be plugged into svn that will parse
those commit comments, and automatically append the commit notice
(including the list of files changed, and links back to viewcvs) to the
I can't recommend specific scripts (all my real experience with this
kind of system is in a cvs/gnats integration, where I found it very
useful), but google is quite happy to help: