Bug triage/2009-02-04

Next meeting: 2009-02-04 at 3pm PST at Bambers Linden's place. See Bug triage for details.

Unimported 1.22 RC / Public Nightly

• VWR-11828 - 3 votes - Sculpts either load extremely slowly or fail to load altogether. - Aminom Marvin
• VWR-11708 - 1 votes - Using the eyedropper causes the source object to highlight in white and stay highlighted - wulfric chevalier
• VWR-11806 - 1 votes - 1.22 RC Viewer for Mac has an extreme broke in in framerate - KatO9 Ninetails
• VWR-10749 - 0 votes - 1.22 can't login anymore on 800x600 screens - Salene Lusch
• VWR-11047 - 0 votes - vwr-1.22.3 Display Settings reset to traditionally undesireable levels. - Arawn Spitteler
• VWR-11254 - 0 votes - "Repeats per face" is handled incorrectly for cylinders with circular hollows - Doran Zemlja
• VWR-11386 - 0 votes - libGLcore random Crashs - Drew Dwi
• VWR-11483 - 0 votes - LlSoundLoop,if we change de sound level on a rezzed prim it does not change the volume until be taken and rezzed again - Cocas Nishi
• VWR-11491 - 0 votes - Editing appearance or changing clothing causes streaming audio to stutter - Tammy Nowotny

Pre-meeting activity

Some issues will be resolved in the course of building this agenda. Rather than deleting them from the proposed agenda, move the issue and associated discussion into the appropriate section below.

Transcript

Transcript is/will be at Bug triage/2009-XX-XX/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: "Viewer 2 Bug Triage" (sorted by LL ID, Created, Last Triaged):
    • https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=12724
  • UI triage:
    • https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=10470 (The selected filter with id '10470' does not exist.)

  (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

<perl>

1. !/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 "* $key - Votes: $votes - $title - $reporter\n";

}

</perl>

• 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