On Mon, May 18, 2009 at 8:01 AM, Jason Winnebeck <[email protected]> wrote: > Chris Nelson wrote:
>> I'd be interested in others' >> thoughts about how this affects Trac core and revisions. > > It's very interesting that you say that because I realized just now that our > Trac environment was moving this way. > [...] Hmmm! This is a very, very, very interesting use case. Now I can see the light at the end of the tunnel. And I suppose this way it is possible to establish explicitly further relationships between milestones themselves. E.g. product A is based on product B so the later must be deployed first and is a blocker for A. > * Use the following wiki for a "milestone" view: > == Ongoing or Upcoming == > > [query:status!=closed&type=deployment Open deployment tickets:] > > [[TicketQuery(status!=closed&type=deployment)]] > > == Completed == > > [query:status=closed&type=deployment Closed deployment tickets:] > > [[TicketQuery(status=closed&type=deployment)]] > And has potential for stats and tickets group stast ;). It's good to know ! -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
