From PerlNet

Pjf is the bug manager for 5.12. He had outlined the following process to triage bugs

The objective is to review as many bugs as possible and mark them as related to the following meta bugs (as DEPENDS ON BY)

• RT 69710 - Perl 5.12.0 - Showstoppers
• RT 70369 - Perl 5.12.0 - Expert assessment required
• RT 70421 - Perl 5.12.0 - Non-critical
• RT 70371 - Perl 5.005 - End of life
• RT 70373 - Perl 5.6.x - End of life

(see http://rt.perl.org/rt3/ this list is current for Perl 5.12)

Set up

1. Get an account at bitcard.org (if you are a CPAN author then you already have an account)
2. Log in at http://rt.perl.org and make sure your account is working
3. Have someone on-hand to give people privileges. Not everyone will have them sorted out before the triage session.
4. It's nice to have the most current production Perl release (currently 5.10.1) available for testing. A lot of old (5.6.x) bugs can just be closed if it's fixed in the most recent release of Perl
5. Break list of bugs into chunks and hand to each group, pair or individual. This avoids double-triage of bugs.

Triage Process

1. Ideally work in pairs or groups
2. Go to the page https://rt.perl.org/rt3/NoAuth/perl5/Overview.html#newissues
3. Open a bug, either from the list that has been given to you, or locate as old a bug as possible
4. Review the bug
   1. Is the issue related to a core Perl component? The command corelist (if available) may be useful. Issues NOT in perl core may be rejected, but try and refer the bug author to the correct module RT queue
   2. It may be reasonable to try and recreate the bug (but don't spend hours), see comment above about having access to current production Perl
5. Decide if the bug is Show Stopper, In need of review, No Action or End of Life
6. Scroll up to the links panel
7. Enter the correct meta bug number into the DEPEND ON BY field
8. On the blue tool bar click on the 'Open'