Bug triage/2009-04-29

From Second Life Wiki

Next meeting: 2009-04-29 at 2 PM SLT at Bambers' Office at Denby. See Bug triage for details.

Contents 1 Today's Triage List 2 Misc Pool 2.1 Imported 2.2 Resolved 3 Transcript 4 Creating An Agenda 4.1 Setting up 4.2 Populating the issue listings section(s)

Today's Triage List

• VWR-13045^[c] - 0 votes - Grey square in IM/friend list, Inventory or Preferances panel - Yann Dufaux
  • Imported
• VWR-12693^[c] - 0 votes - RelWithDebInfo build fails on MacOS due to the too large size of output - Alissa Sabre
  • Last Triaged date added
• VWR-12960^[c] - 0 votes - Fisheye effect camera - Tayra Dagostino
  • Resolved - Needs more information
• VWR-12914^[c] - 0 votes - SL hangs quite often when doing a snapshot - Silver Key
  • Resolved - Needs more information
• VWR-12965^[c] - 0 votes - Copy to inventory from notecard crash viewer - Tayra Dagostino
  • Resolved - Needs more information
• VWR-12974^[c] - 1 votes - Water Reflections Visible Through Shiny/Full Bright Objects - Dirk Talamasca
  • Imported
• VWR-12984^[c] - 0 votes - 1.23 Public Nightly: Water flickers and disappears in patches around 1000 meters - Harleen Gretzky
  • Imported
• VWR-12936^[c] - 0 votes - Get Top Script in Debug menu (Region/Estate) give all script as 0,00ms - Tayra Dagostino
  • Resolved - Needs more information
• VWR-8748^[c] - 1 votes - rapid flying, while zoomed out, over a period of time, causes the viewer to hang on drawing and then crash with rapid direction change - Cummere Mayo
  • Resolved - Fixed
• VWR-12968^[c] - 5 votes - Disabled popups will become active again on relog - Sugarcult Dagger
  • Known Issue
• VWR-13019^[c] - 5 votes - Textures Slow To Load - TriloByte Zanzibar
  • Resolved - Duplicate

Misc Pool

Misc Pool

Imported

Resolved

Transcript

Transcript is/will be at Bug triage/2009-04-29/Transcript

Creating An Agenda

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