Bug triage/2009-03-16

Next meeting: 2009-03-16 at 12:00 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)

Hot by Vote

High Voted Bugs

VWR-8597 - Votes: 13 - Viewer freezes for minutes at a time - Mimika Oh
- Imported
VWR-5251 - Votes: 7 - Beacons fail to show on attachments - Henri Beauchamp
- Imported
VWR-3678 - Votes: 6 - Add find/replace feature for notecard edit windows - Tijn Erde
- Imported

Patches

VWR-12427 - Votes: 0 - A non-ASCII character in boost header file makes viewer build to fail on non-US versions of Windows - Alissa Sabre
- Last Triaged date added
VWR-12385 - Votes: 0 - Building hotkeys to include next/previous prim in a link set - Techwolf Lupindo
- Tied to VWR-9287 which is imported
VWR-12454 - Votes: 0 - Given notecards lack the "Save" button while it is possible to save them via the CTRL S keyboard - Henri Beauchamp
- Imported

Misc Pool

WEB-989 - Votes: 1 - Blog illogically requires secure connection to view rather than just to login and comment - Gordon Wendt
- Imported
VWR-1168 - Votes: 6 - Misplacement of attachments using llSetPos()+llSetLocalRot() - Vance Vega
- Resolved - Needs more info
SVC-2313 - Votes: 5 - Your last location is not currently available. - Kontor Jenkins
- Imported
VWR-6996 - Votes: 1 - Mac: Can not remember VRAM over 64MB setting. - Capucchy Streeter
- Resolved - Won't Fix
VWR-2775 - Votes: 1 - Unpredicatable crashes in Linux-client since version 1.18.3.5 (1.18.3.4 was ok) - Marcoh Larsen
- Resolved - Needs more info

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/2009-03-16/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