Bug triage

12:00 NOON SLT

2:00 PM SLT

2:30 AM PLT

Triage Attendance Guidelines

• We work off of prepared agendas that can be found in the triage links above. If you have an item you'd like to discuss, please add it to the agenda prior to the meeting.
• All triages are done in chat so we are able to keep the transcripts. We ask that voice be turned off so those not using voice may participate in all conversations.
• Since some people are on slower machines, we ask that all poofers and particle effects be turned off please.
• Please turn off all gesture sounds.
• Please do not send private IMs to the Lindens running the meeting as they are not able to answer them and run the meeting.

Process notes

During the actual bug triage, we step through each issue one at a time, identifying which issues deserve priority for closer attention. It's a subjective process, but here are some of the criteria evaluated:

• Does this bug have a large impact on users and/or a lot of JIRA votes?
• Is there enough information for developers to address it (i.e. a quick repro), or is more information needed?
• Is there a patch attached that addresses the issue?

A triage meeting may find bugs that don't have a proper reproduction or are duplicates of other bugs. These issues may be marked as "Resolved" as "Duplicate" or "Cannot Reproduce", as appropriate.

• If a bug has no repro, it will be marked "Resolved/No Repro", but the bug isn't closed.
  • All bugs marked "resolved" are implicitly assigned to the reporter.
  • If the reporter agrees (is unable to provide a consistent repro), they close it. If not, they reopen with a repro

We take the number and quality of repros into account, so if there's something you want to make sure we get around to, please add whatever debug information you can. Some attention is paid to the number of votes (where really highly voted issues will probably get noticed), so vote for the issues that you think are most important.

Lindens: if you are aware of a duplicate issue filed internally, please enter the number of the internal issue into the external tracker.

Setting an agenda for a triage meeting

Community members generally collaborate on the agenda for bug triage meetings. Here's how you can quickly fill in an otherwise blank agenda:

Setting up

• Go to Bug_Triage/YYYY-MM-DD where YYYY is the four digit year code, MM is the two digit month code, and DD is the day code
• Write and save {{subst:Triage Template}} as the only content of your new page. This will copy the complete markup from Template:Triage Template as a starting point for your agenda.
• Fill in the relevant time, date, and location info for the upcoming meeting. The easiest way to do this is to copy the entire block of information from an earlier meeting of the same type (RC, regular, etc...) and modify the date and time as needed.

Populating the issue listings section(s)

• Look at the results of one of these queries
  • General triage: "Bugs, sorted by LL ID"):
    • https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=10155
  • UI triage:
    • https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=10470

  (Note: there's no hard and fast rule that says these are the only valid queries. If you feel there's a better query one particular week, use that.)

• Save a copy of the XML version of the query
• Run this perl script on the xml file

 
#!/usr/bin/env perl
use XML::Simple;
 
my $bugs = XMLin($ARGV[0]);
 
foreach my $item (@{$bugs->{channel}->{item}}) {
  $title = $item->{title};
  $title =~ s/^\[[^\]]*\] //;
  $key = $item->{key}->{content};
  $votes = $item->{votes};
  $reporter = $item->{reporter}->{username};
  print "* {{jira|$key}} - Votes: $votes - $title - {{User|$reporter}}\n";
}
 
 
 

• Pick a reasonable cutoff point, and copy the output into the appropriate section of your newly created page.

• if you do not have access to a perl interpreter. There is a ported version of the script on PHP, located here: http://jirafiller.technokittydevelopment.com/ made by roberto salubrius

We usually get through about 20 issues in a meeting (+/- 10). By getting involved in the agenda creation process, you can help make sure we discuss the 20 most important issues rather than a random 20.

Best Meeting Times

Help us choose the best meeting times. If you regularly attend triages (or would like to do so), please add yourself to this list and mark off the most convenient (Second Life Time) hours for yourself:

  Name               Weekday 06 09 12 15 18 21   Weekend 06 09 12 15 18 21
  Able Whitman                         *  *  *               *  *  *  *
  Alissa Sabre                *  *     *                  *              *
  Boroondas Gupte                   *  *                  *  *  *  *
  Celierra Darling                     *  *  *                  *  *  *  *
  Daedalus Young                    *  *                  *     *  *
  Dale Glass                     *  *  *  *               *  *  *  *  *
  Dana Fagerstrom             *  *  *
  Gordon Wendt                   *  *     *  *               *  *  *  *  *
  Haravikk Mistral                                        *  *     *
  Henri Beauchamp             *  *  *                     *  *  *
  Jacek Antonelli                   *  *  *  *                  *  *  *  *
  Jason Giglio                      *  *  *  *                  *  *  *  *
  John Hurliman                     *  *  *  *                     *  *
  Nick                        *  *  *  *                  *  *  *  *
  NickCA Dittmann                   *  *  *  *                  *
  Meni Kaiousei                     *                           *
  Maggie Darwin                           *                  *  *  *  *
  Techwolf Lupindo               *                           *  *  *  *  *
  Arabella Steadham                                                *  *  *

Notes from previous triages

See Category:Bug triage