Bug triage/2007-10-22

Next meeting: 2007-10-22 at 3pm SLT in Hippotropolis. See Bug triage for details.

This week's theme... Old bugs. Bugs only live for a short time, but they reproduce quickly. Some of these ancient bugs have withstood the test of time, some haven't. Your mission is to figure out which have and which haven't.

Fast Track Import

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

• WEB-179 - Votes: 0 - Mailing list page still has paragraph about and link to defunct software update list - Jayden Emmons

Misc Pool

• WEB-166 - Votes: 4 - Land Store map is extremely difficult to read - Steve Mahfouz
• SVC-120 - Votes: 0 - Objects -> Permissions -> Modify Rights -> affects Return ability - Gigs Taggart
• WEB-86 - Votes: 3 - Transaction History Total Bug when paying self owned object - Gypsy Paz
• VWR-2426 - Votes: 1 - Missing character in email sent with llEmail - Simil Miles
• SVC-128 - Votes: 1 - automatic deletion of group leaves any owned property in "limbo" - Ahzzmandius Werribee
• MISC-150 - Votes: 3 - When a child prim moves with llSetPos, any avatar sitting on it does not move. - Gigs Taggart
• SVC-141 - Votes: 1 - Restrict Pushing disallows pushes from objects set to group - Lex Neva

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/2007-10-22/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