Bug triage/2008-06-02

Next meeting: 2008-06-02 at 12 PM SLT at Hippotropolis Meeting area^🖈. See Bug triage for details.

Hot by Vote

High Voted Bugs

• SVC-2359 - Votes: 12 - Capped IMs can cause inventory loss - Matthew Dowd
  • Imported - Assigned to Triage
• VWR-5791 - Votes: 14 - Multiple local lights cause flickering with Flycam - Zolute Infinity
  • Imported - Assigned to Triage
• SVC-2426 - Votes: 16 - llPushObject in attachment pushing the person wearing it has stopped working with update 1.22.1 - darling brody
  • Asked if the reporter is experiencing the same problem in the latest RC
• VWR-7329 - Votes: 17 - 1.20 RC7 WatchDog forces crash on login if wait time is longer than 10 seconds - Karl Dorance
  • Imported - Assigned to Triage
• SVC-1060 - Votes: 12 - Some parcels are not indexed in new search - Rifkin Habsburg
  • Asked if the reporter is still experiencing this problem
• VWR-6352 - Votes: 12 - Camera Springiness Control (in prefs) not responding / Collision detection causing cam to jump very frequently while moving - maxwell graf
  • Imported - Assigned to Triage
• SVC-126 - Votes: 13 - In world map image is not updating - Gigs Taggart
  • Bridie talking with developers on this
• VWR-7403 - Votes: 17 - Cannot log in to the Release Candidate 1.20.8 - miran ashbourne
  • Imported - Assigned to Triage
• MISC-1231 - Votes: 174 - Missing Cultures & Communities from SL5B - Vint Falken
  • Talking with Robin & GTeam on this issue

Patches

Patches

• VWR-7362 - Votes: 0 - Add LSL constant EMPTY_KEY as (key)"""" please - meade paravane
  • Waiting for more votes/interest
• VWR-1363 - Votes: 9 - Add ""Return Object"" to the Tools menu - McCabe Maxsted
  • Imported - Assigned to Triage

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-06-02/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