Emmanuel Blot wrote: > Hi All, > > What's the current policy with ticket renaming on t.e.o.? > > At some point in the past, some lead developer wrote that tickets that > were created w/ an attached patch may contain the [PATCH] keyword in > the summary, while existent tickets that were attached a patch after > their creation should not be renamed. > > IMHO this rule should be kept, as it makes ticket history easier to > follow w/ email clients for instance. > > Any thoughts ? >
Well, I personally don't care that much and I find this rule to be a bit arbitrary. If one wants to stick with the existing rule and nevertheless trigger an e-mail notification (to compensate the known defect #2259 - no notification on attachments), one alternative is to add the "patch" keyword. As for the e-mail client argument, I think it's not a strong one, as summary changes are often needed in order to fix a poorly worded summary, or to precise the focus of a ticket if it changes over time. And we should take the habit of fixing them more often, as this facilitates a lot working with ticket reports. To answer Remy, "How do you mark a ticket as having a patch for review?", "review" could be used as well, but there's the distinction that "patch" is used when the patch is coming from contributors and "review" when its coming from team members. Of course, that distinction is quite as arbitrary as the "[PATCH] for new ticket only" one ;-) See http://trac.edgewall.org/wiki/TracTicketTriage for more... -- 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 -~----------~----~----~----~------~----~------~--~---
