Bug triage/2007-10-29

From Second Life Wiki
< Bug triage
Revision as of 13:18, 30 October 2007 by Alexa Linden (talk | contribs) (→‎Misc Pool)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Next meeting: 2007-XX-XX at TIME and PLACE (FIXME). See Bug triage for details.

Fast Track Import

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

Hot by Vote


Misc Pool

  • VWR-106 - 4 votes - Video Capture hasnt worked for quite a while - Chilko Tardis
    • Closed - Duplicate of VWR-2096which has already been imported
  • SVC-29 - 34 votes - XMLRPC sporadically (but usually) very slow - Apotheus Silverman
    • Already imported - SL33824. This link has been corrected
  • VWR-249 - 3 votes - No warning when attaching objects which will replace existing attached objects - Emerald Geiger
    • Changed to feature request. Imported - Assigned to Benjamin Linden
  • VWR-417 - 6 votes - Avatar skins load twice - Eric Ruban
    • Leave as-is. Marking with "Last Triaged" Date.
  • VWR-500 - 4 votes - Searching inventory for "copy", "modify" etc brings up everything. - Gigs Taggart
    • Changed to feature request
  • WEB-87 - 5 votes - Land Store Map is not Updating - Gigs Taggart
    • Leave as-is. Relates to WEB-166 and other Land Store Map related issues. Added Last Triaged Date.
  • SVC-126 - 7 votes - In world map image is not updating - Gigs Taggart
    • Closing - Need more information. Need specific region
  • SVC-130 - 3 votes - CC needed with PayPal, contradictory to what sl website says - 3dziggy oh
    • Moved from SVC to WEB. Imported and assigned to Beez Linden
  • WEB-94 - 0 votes - credit card details that have been used for 3 years are now unauthorized - Fau Ferdinand
    • Resolved. Misfiled. Posted link to support.
  • VWR-545 - 6 votes - Controls freeze / inventry incomplete / Menus freeze / avatar wrong sex! - ratus raymaker
  • SVC-145 - 6 votes - Existing Hollow Box Prims Have Changed from 95% Hollow to 94.9% Hollow - Gatz Morang
    • Closing. More information needed. Is this still happening? Repro steps?

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 is/will be at Bug triage/2007-10-29/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)


  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";



  • Pick a reasonable cutoff point, and copy the output into the appropriate section of your newly created page.