The issue tracker on parrot/parrot had over 500 tickets last week. I would like to get that number down to 450 for the release, maybe 400 by 4.5.0. Could all developers please look through the list and tackle any low-hanging fruit? Getting rid of small, vague or fluff tickets helps to clear clutter away and expose the more pressing issues.
Here are some guidelines: 1) If you see a ticket that you can work on and doesn't currently have an owner, please assign yourself to it. It's easier to sort through a short list of "tickets assigned to me" than it is to search through the whole queue for items. 2) If the ticket is already fixed, is unfixable, or refers to a subsystem which no longer exists, close it 3) If the ticket is too vague or is not actionable, either close it or post a request for more information. 4) If the ticket is a wishlist item consider closing the ticket and adding the idea to the wiki on an appropriate tasklist page (create a new page if you need. It's easy to do) 5) If the ticket refers to old platforms that we do not support or old dependencies that aren't used or that we cannot test or anything else that made sense three years ago but isn't relevant or important now, consider closing it or asking for more information. 6) If the ticket can be fixed and closed easily, please do. 7) RFC tickets, or tickets requiring input can be assigned to cotto (for architectural stuff) or myself (for project management and interfaces). If some other developer seems like a natural fit, assign it to them (and they can assign back out if necessary). 8) Please check the tags on the ticket and make sure correct metadata is attached. Information about priority, platforms, subsystems and other tags can be very valuable for sorting and searching. If everybody closes one or two tickets in the next week, we can easily be down to 450 by the 4.4.0 release on Tuesday, and continue going lower after that. Thanks, --Andrew Whitworth _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
