Noah Kantrowitz wrote: > Are there objections to closing #31 and #886? MasterTickets implements > the feature fairly well I think, and its big enough that I'm not yet > in favor of core inclusion.
I'd be OK for #31, but certainly not for #886. #886 / SubTickets is more about having a way to compose hierarchical groups of tickets and show the progress on them, in a more flexible way than just the 2-level hierarchy of Milestones and Tickets. AFAICT, by looking at the plugin code, there's no such thing there, only blocking/blocked by relationships, which indeed correspond to a simple form of #31. For #31, I'm somewhat reluctant to close a ticket discussing a major feature by a "wontfix / use a plugin instead" statement. But on the other hand, there are so many open tickets in Trac that this is probably the best we can do at this point. So +1 from me for closing that ticket and advising to use MasterTickets plugin (but this is more of a trust thing than anything else, as I haven't yet tested the plugin myself). -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
