[openbeos] Re: Trac SVN revisions

Hi,

On 11/29/06, Jérôme Duval <korli@xxxxxxxxxxxxxxxx> wrote:

> On 11/29/06, Jérôme Duval <korli@xxxxxxxxxxxxxxxx> wrote:
> > 2006/11/29, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>:
> > > thanks to Waldemar, Trac now identifies references to SVN revisions in
> > > comments if they follow the usual style, that is, for example r1234.
> > > So, if you refer to SVN revisions in Trac, please always write it that
> > > way if the change is important for the bug, ie. "Fixed in r1234" is
> > > then much more helpful than "Fixed in rev 1234" or "Fixed in 1234" :-)
> >
> > Does this mean I can search bugs based on a SVN revision ?
> > It is definitely useful for generating a changelog.
>
> No, unfortunately not. But I also don't know how you imagined this to
> work. Doesn't CIA already do what you want?

I thought a "Fixed in revision(s)" field would be good enough.
It would be useful if one wants to generate a release notes document
(with impacting revisions) like this :
http://struts.apache.org/1.2.9/userGuide/release-notes.html
What do you think ?


How do you intend to extract that information from Trac? And will you
not still miss quite a few changes which were not in Trac and thus
need a review of the repo changes?
But most importantly: why is it important (regarding release notes) in
which revision it was fixed? IMHO, it's more than sufficient to use
milestones for this. We could have milestones for each minor release,
so in the end you'd have everything accessible through the Roadmap
page in Trac (which can be used to list all closed tickets for the
milestone). We could also introduce the convention that you must
mention the release number in which you closed the ticket (if it's
really needed) or use Trac's integrated wiki to keep track of release
numbers and their respective tickets.

Would that be good enough (and keep the Trac UI simple)?

Bye,
Waldemar Kornewald

Other related posts: