Bug triage/2008-09-29

Next meeting: 2008-09-29 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)

Hot by Vote

High Voted Bugs

SVC-1253 - Votes: 85 - users sitting on prims, which are set to phantom are not affected by damage. - Drew Dwi
- Imported - Assigned to Andrew Linden
SVC-2502 - Votes: 11 - (Selected types of) Scripted Prim Torture no longer Works!!! - Strife Onizuka
- Imported - Viewer
VWR-5949 - Votes: 32 - Out of Memory Error - alan edelman
- Imported - QA.

Patches

VWR-9340 - Votes: 0 - Place ""Buy..."" in the top level pie menu - McCabe Maxsted
- Imported - Assigned to Rx

Misc Pool

SVC-3146 - Votes: 2 - Server is not sending enough data for texture discard levels - Eddy Stryker
VWR-9347 - Votes: 0 - Texture Memory preference keeps resetting. - Zauber Exonar
VWR-5023 - Votes: 0 - Everything appearing posterized with recommended settings - Merlot Andalso
VWR-8780 - Votes: 0 - Russian translation: some menu names can't be translated - Ian Kas
WEB-187 - Votes: 1 - spurious --> symbols in transaction history - Lex Neva
VWR-1306 - Votes: 1 - Texture blending issue at region border - Sean Linden

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-09-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: "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