Bug triage/2010-01-25

From Second Life Wiki
< Bug triage
Revision as of 13:44, 25 January 2010 by Alexa Linden (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search




Next meeting: 2010-01-25 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-6484 - Votes: 19 - Minimap height indicators all show "lower than me" if over the old 768 build ceiling - Buckaroo Mu
    • Status?
  • VWR-4137 - Votes: 22 - Date columns in tables are sorted alphabetically - Celierra Darling
    • Only two of the three were fixed.
  • SVC-4937 - Votes: 29 - "The server is experiencing unexpected difficulties" error when saving a notecard inside a prim. - Bones Outlander
    • Requesting status update be posted to pJIRA
  • SVC-3514 - Votes: 35 - llLoadUrl (and other LLMessageBox-generating functions) should be per-agent throttled, not delayed - Darling Brody

Hot by Vote

High Voted Bugs

Misc Pool

Misc Pool

  • SVC-388 - Votes: 5 - llGetScriptName() returns script's old name - Lex Neva
  • SVC-4860 - Votes: 2 - when teleport routing is set to blocked people can not enter directly into parcel when i tp them myself - Alexandrea Fride
  • VWR-12870 - Votes: 2 - Loggong out of linux viewr version 1.22.11.113941 hangs computer - Corin Clary
  • VWR-16294 - Votes: 7 - When using llDetachFromAvatar() after teleport the objects still appears attached to the user but not to other residents and becomes almost impossible to detatch. - Madeline Kaligawa

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-01-25/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)

<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.