Bug triage/2007-12-19

Next meeting:

2007-12-19 - Release Candidate triage - Wednesday, 3pm PST at Bridie Linden's house.

Import?

(Bugs reported in 1.18.6.1 Release Candidate — consider for import?, sorted by votes)

VWR-3864 - Votes: 0 - Viewer Does Not Maintain Preferences - vaguegirl Petty
- Imported - Assigned to Aric Linden
VWR-3837 - Votes: 0 - Keyboard forcus goes to a meaningless location on the login screen - Alissa Sabre

Imported - Assigned to Aric Linden. Cross-referenced to VWR-3838

VWR-3868 - Votes: 0 - Particle system angle resolution lower than expected - Creem Pye
- Closed - Needs More Info
VWR-3801 - Votes: 0 - Wrong primitives usage display - bigmanu greene
- not new in RC
- waiting for resident to give me locations so I can check this in english
VWR-2430 - Votes: 1 - SecondLife disables DPMS under Linux - CrazyTB Oh
- not new in RC
- Imported - Assigned to Tofu Linden

Patches

VWR-3808 - Votes: 0 - Cannot login to private servers with new login system - Michelle2 Zenovka
- has patch

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/12-19-2007/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