Bug triage/2009-06-01

Next meeting: 2009-06-01 at 12:00 NOON 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)

• - VWR-12630 - Votes: 1 - texture rendering is slightly but infuriatingly broken - Edward Vellhi

Hot by Vote

High Voted Bugs

• - MISC-2855 - Votes: 29 - Stop the spamming MoneyOrb Script whitch send to every people automaticly and try open secondlifey.com - Holger Gilruth
• - SVC-4308 - Votes: 16 - Throttle incorrectly applied to llOwnerSay - darling brody
• - VWR-13532 - Votes: 14 - CHANGED_REGION_START is not being recognised - Haverlock Borkotron
• - MISC-46 - Votes: 13 - Unable to view notecards: "Insufficient permissions to view notecard" - Alec Antwerp
• - VWR-2726 - Votes: 13 - all inventory folders open - vida nemeth
• - SVC-914 - Votes: 12 - CHANGED_TEXTURE is not triggered when texture is changed via script - Jacek Antonelli
• - SVC-3162 - Votes: 10 - Avatar gets stuck in pre-jump state and slides along the ground waiting to jump. - Jathra Vanmoer
• - VWR-4913 - Votes: 10 - Items not returning to Lost and Found folder - eren padar

Misc Pool

Misc Pool

• - MISC-2862 - Votes: 1 - Strong passwords not usable with jira, xstreet or forums - Fauve Diavolo

• - MISC-1978 - Votes: 9 - Not showing payment info on file on profile - Ricco Paulse

• - VWR-1546 - Votes: 8 - Group Chat says only participant when there are other participants. - Rascal Ratelle

• - VWR-8143 - Votes: 5 - Colored Spots on Objects and Avatars since the rolling restart on Friday the 11th of July - nelly janus

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/2009-06-01/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