We have a new mailing: list [EMAIL PROTECTED], which will receive change notices for the Trac ticket queue. If you want to follow the ticket changes, subscribe at:
http://lists.parrot.org/mailman/listinfo/parrot-tickets I also updated the Trac site so Trac tickets have the flags we commonly use on RT. I took the opportunity to clean up and didn't include all the old flags. If you want a flag ported over or a new flag added, just let me know. This means we're ready to use Trac for tickets. You can create an account for yourself at: https://trac.parrot.org/parrot/register New tickets should go to Trac. We'll port old tickets over the next few months. (Consider it an opportunity to filter. If a ticket is a valuable ongoing task, port it to Trac. If it can be quickly resolved, resolve it rather than porting it. If the ticket is vague or outdated consider rejecting it. If it's a ticket for a particular language, leave it, we'll likely move it to a separate queue for the language. etc...) One substantial change to the workflow: Trac won't follow comments posted by email, so if you want your comments to be added to the ticket, make them through the web interface. If this turns out to be too painful, it looks like there are some extensions for Trac to allow it to accept submissions by email. But, this might turn out to be an advantage, encouraging submitters to include the helpful flags for platform, severity, etc, and encouraging long discussions on the mailing list to be summarized in the ticket (rather than getting a copy of every post) to make it easier to review/close tickets. We'll see what works best and adjust as needed. Allison _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
