Bug triage/2008-08-25

Next meeting: 2008-08-25 at 12 PM SLT at Hippotropolis Meeting area^🖈. See Bug triage for details.

Fast Track Import

(Move bugs here that have solid repros, or valid patches that you have reviewed)

VWR-9023 - Votes: 1 - llResetScript in touch_start() results in double touch_start() event
SVC-2990 - Votes: 6 - Listen events persist between states in LSL2

Hot by Vote

High Voted Bugs

VWR-7509 - Votes: 11 - Script error when alot of sounds are playing - Iexo Bethune
- Requested the maker and model of the plane for testing
VWR-8717 - Votes: 22 - Crashes after login when using ATI Catalyst 8.8 - Dandare Daniels
- Imported - Assigned to Zen Linden
VWR-8337 - Votes: 33 - Slows to 1 frame every 2 sec after login in the second time - skidz tweak
- Resolved - Duplicate of VWR-8717
VWR-5949 - Votes: 15 - Out of Memory Error 1.19.1.2/3/4 - alan edelman
- Last triaged date added

Patches

VWR-2710 - Votes: 2 - Turkish Beta Language Pack For Second Life Viewer - Vixen Heron
- asked to have a post when the file has been updated

Misc Pool

VWR-8761 - Votes: 0 - Object description change to null is not saved - Gellan Glenelg
- Imported - Viewer
VWR-8283 - Votes: 0 - UI scales in windowed mode, even if deselected - Lanita Wingtips
- Changed to Feature request

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.

Imported

Resolved

Transcript

Transcript is/will be at Bug triage/2008-08-25/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>

!/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