On Wed, Dec 10, 2008 at 5:21 PM, Andy Dougherty <[EMAIL PROTECTED]> wrote: > This is just a general suggestion: I understand that moving to Trac is a > good opportunity to clean out old RT tickets. However, when moving > tickets to Trac, please do be careful not to throw out important > additional information.
+1 > I don't know if there's an easy way to bring over > an entire old ticket, but sometimes there's a lot of useful information > buried down below the first entry. Agreed. Here's my plan for moving things over: If at all possible, resolve the ticket in place, either by rejecting it or (gasp) resolving it. If it's a trivial one line TODO, that can be moved over without much thought. (However, reject it or do it if possible.) If you're trying to help out on ticket triage, don't add comments to the ticket like "what's the status?" unless you have some familiarity with the ticket. If possible, assign the old ticket to the person you think might be responsible for it. (For example, I've assigned some RFCs to allison hoping she'll reject them. =-) With what's left, moving items which are listed on one of the RoadMaps in the new trac wiki is a priority, so we can get the automagic roadmap working. If you have to move a ticket and can't let it stay in RT any longer, and there's a nontrivial amount of information; link back to the original ticket. If it's a small amount, cut and paste it in. Once we get through all the closable tickets, we can re-evaluate how we're going to move things. Someone should take this message and create a trac wiki page for RtMigration. -- Will "Coke" Coleda _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
