Bug triage/2008-08-27

Next meeting: 2008-08-27 at 3pm PST at Bridie Linden's house.

Import?

(Bugs reported in 1.21 Nightly Release — consider for import?, sorted by votes)

• VWR-8513 - Votes: 3 - 1.21 nightly: orange color for object chat is ugly- McCabe Maxsted
• VWR-8772 - Votes: 3 - 1.21 Nightly: Color gradient pick does not register all mouse clicks - Shibari Twine
• VWR-8516 - Votes: 2 - 1.21 nightly: new chat transparency setting interferes with HUDs on the right - McCabe Maxsted
• VWR-8739 - Votes: 2 - Freeze when Advanced->Rendering->Info Displays-> Bboxes selected - Opensource Obscurer
• VWR-8742 - Votes: 1 - 1.21 nightly: Crash (assert_glerror: GL Error:out of memory) when clicking URL - Gellan Glenelg
• VWR-8784 - Votes: 1 - client is crashing in enviroments like the Hair Fair 2008 and stores like Dejavu Designs - Sugarcult Dagger

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

• VWR-8775 - Votes: 3 - Texture Deformation and Object Bounce/Jiggle at high altitudes - Poe Tatum
• VWR-8773 - Votes: 2 - Closing parenthesis ")" breaks urls - McCabe Maxsted
• VWR-8340 - Votes: 1 - Viewer 1.20 crashes with the Nvidia 8600 card - Ramzi Linden
• VWR-8597 - Votes: 1 - Viewer freezes for minutes at a time - Mimika Oh
• VWR-8406 - Votes: 0 - Double crash report dialog (Linux) - Vex Streeter
• VWR-8411 - Votes: 0 - Viewer 1.20.15-3D Graphics quality degraded - Qiana Tuqiri

Fast Track Import

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

Hot by Vote

High Voted Bugs

Patches

Patches

Misc Pool

Misc Pool

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/2008-08-27/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