Bug triage/2007-08-06

Next meeting: 2007-07-30. Host: Rob Linden See Bug triage for details.

Fast Track Import

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

Misc Pool

Leftover from 2 weeks ago:

• VWR-289 - Votes: 4 - URLs for video media streaming need to be URL-encoded or stream doesn't work - Gwyneth Llewelyn
  • Waiting for comments from Able Whitman
  • Needs more discussion on SLDev
• WEB-67 - Votes: 3 - Unable to report bug that essentially depends on presense of non-ASCII characters - Alissa Sabre
  • alread imported
• VWR-298 - Votes: 1 - Practically impossible to enter Japanese text when viewer is running full-screen on MacOS - Alissa Sabre
  • alread imported
• VWR-301 - Votes: 1 - Transparent objects - touch events can not be triggered - Cappy Frantisek
  • Moved to 'New Feature'
• VWR-304 - Votes: 0 - Attachments flash in mouselook - Huns Valen
  • Imported after changing priority to 'small'
• VWR-310 - Votes: 2 - On viewing a MySpace page with Audio in the Web Tab of profiles the audio keeps playing after the profile is closed. Nothing can stop the audio short of exiting. - Jayden Beresford
  • Resolved 'needs more info'
• SVC-72 - Votes: 6 - Failed login - logs in, but unable to use system - Marion Rickenbacker
  • 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.

Resolved

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