Hi Waldemar,
> > 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?
Minor releases usually only fix bugs which are in Trac.
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.
I just don't want to loose the actual subversion change information. Release notes could include the name of the guy who fix the bug (from the revision, and not the one who closed the bug). If revision numbers are in ticket comments, will you be able to have them appear in your roadmap report ?
Would that be good enough (and keep the Trac UI simple)?
Simple would be a single textarea where one can enter anything :) Is there a way to know which comment was added with the resolve/close change of state of the bug ? This way you could know this is the actual revision which fixes the bug. Bye, Jérôme