In addition to the work I and others have done over the weekend to close out what can be closed simply and confirm/close everything else, I've been working to make the RT queue a little more useful for prioritizing effort. Some changes:
* Added [PATCH] to the subject line where a ticket contains a proposed patch * Added [needs upstream fix] line where the ticket depends on another distribution * Re-prioritized tickets (see below) These changes make it easy (at least for me) to skim over a severity-sorted list of tickets and see what needs doing. I've tried to use the following logic, more or less, for prioritizing ticket "severity": * Critical -- OMYGODIBROKECPAN issues; installing M::B cripples subsequent module installations * Important -- M::B won't install or function correctly on a major OS or for a major class of distributions (e.g. XS) * Normal -- core user actions (build/test/install) or author actions (meta/manifest/dist*) broken in specific but not widespread situations or where clear workarounds exist (e.g. using Build.PL instead of M::B::Compat Makefile.PL) * Unimportant -- author 'helper' actions broken, documentation issues, things that annoy authors using M::B * Wishlist -- new features, options or DWIMmery On that basis, I think we're down to 5 Normal tickets (plus 1 I'm leaving open until 0.34 so we stop getting new tickets about M::B 0.33 not installing with its Makefile.PL). There are 18 Unimportant issues and 25 Wishlist items. I'd appreciate people's input on whether any of the remaining Normal tickets really need to be addressed before 0.34. Thanks, David
