Bug triage/Wednesday Agenda

Next meeting: 2010-05-19 at 2.00 PM PDT at Bambers' Office at Denby. See Bug triage for details.

Fast Track Import

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

Misc Pool

VWR-20531 - 16 votes - Avatars have fat ankles - Lindal Kidd

VWR-20510 - 8 votes - you can only output a landmark from shared media if the region is only one word, otherwise viewer2.0 will not recognise it as a landmark address. - loki eliot

VWR-20141 - 7 votes - F2 shortcut for "Rename" doesn't work in Sidebar > Inventory - Opensource Obscure

VWR-20236 - 6 votes - Group Chat Failure Message Freezes Viewer - Calica Siamendes

VWR-20185 - 6 votes - Alpha masks sometimes have visible "lines" at some texture seams. - Asami Imako

VWR-19014 - 6 votes - When exiting second life viewer 2 the screen colors scramble. Some menus are slightly discernable.Only resolution so far is to reboot computer. - Sid Canonmill

VWR-20390 - 5 votes - Avatar texture layers stay blurry - Hugh Helendale

VWR-19847 - 5 votes - High Rez Snapshots do not allow selection of "save as" location or name after the first snapshot is taken - Belladonna Eberhardt

VWR-19487 - 5 votes - Estate Managers unable to freeze / eject without admin tools enabled - Drew Dwi

VWR-18791 - 5 votes - Nearby Chat "emotes" are written to the chat log file on disk literally. - Ardy Lay

VWR-18472 - 5 votes - Only minimal feedback given using Content -> Permissions to change object inventory permissions - Stickman Ingmann

VWR-17453 - 5 votes - Cannot create clothes in appearance - jonathan yap

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/2010-05-19/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