Bug triage/2009-10-19

From Second Life Wiki
Jump to navigation Jump to search

Next meeting: 2009-10-19 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)

  • SVC-4937 - Votes: 1 - Server is experiencing unexpected difficulties error when saving a notecard inside a prim. - Bones Outlander

Hot by Vote

High Voted Bugs

No issues with votes over 10

Misc Pool

Misc Pool

  • VWR-15821 - Votes: 3 - All 1.23 Viewers (1.23.4/1.23.5) Have SEVERE graphics lag with ATI Video. You lose anywhere between 4 and 15 FPS. On a laptop this cripples your ability to play SL - Andromeda Recreant
  • WEB-1344 - Votes: 1 - "Age verification page claims payment info is valid identification of age, sets adult access but not age verified" - Murry Soothsayer
  • VWR-4424 - Votes: 3 - Objects owned by me cnt be used by others if the object rezzes objects to operate (ie poseballs or blank notecards/scripts) - LadyLutha Harlow
  • SVC-3071 - Votes: 2 - "A recent change generated ""Too Many Listens"" script crashes, then script cannot be reset with llResetOtherScript." - Ralph Doctorow
  • SVC-3202 - Votes: 2 - drag/drop destination prim in linkset object varies based on type of asset - Nava Muni

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/2009-10-19/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.