On Wed, 2006-04-19 at 13:38 -0700, Jeff Rodenburg wrote: > Apologies if this is a repetitive newbie question, but I can't locate > an answer to what seems to be a core task. > > We associate svn changesets to tickets, which in turn are associated > to a Release. When we're ready to migrate those changesets (from our > trunk) to production (release branch), we pull the changesets for the > given Release (not all changesets are released together). I need an > automatic way of pulling the changeset list for the given Release. Is > there a standard report that does this or another way of gathering > that info?
So, if I understand, you want to get a list of all changesets related to all tickets for a particular Trac milestone. I'm afraid Trac doesn't provide a way to do that at the moment. I think that part of the problem is that most people don't manage releases from Subversion in that manner. Subversion tends to lead itself to a more linear development model where all the changes for a release are made on a single branch. Then the branch is tagged when the release is made. Some of the distributed version control systems are better at supporting the method you described above since they make it easier to pull individual patches between branches. So, typically on Trac you could see the changes for a release just by looking at the revision log for the branch where it was worked on. For example, these were the changes made to Trac between 0.9.4 and 0.9.5: http://projects.edgewall.com/trac/log/branches/0.9-stable?action=stop_on_copy&rev=3202&stop_rev=2917&mode=stop_on_copy -- Matthew Good <[EMAIL PROTECTED]> _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
