Bug triage/2010-05-24

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

Next meeting: 2010-05-24 at 12:00 PM (noon) PDT 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)

Hot by Vote

High Voted Bugs

  • SVC-5428 - Votes: 52 - High Packet loss, Rubberbanding, Script runtime stops, various other issues since 1.36.2 emergency release. - Karoline Merlin - Last Triaged: 5/3/2010 9:11 AM

Misc Pool

Misc Pool

  • SVC-5713 - Votes: 4 - ParcelAccessListReply packets have no reliable end of list indication, leading to possible data loss - Dale Glass
  • SVC-4812 - Votes: 3 - Top scripts count object double when sitting on it resulting in double counting of total script time for the sim - Zuleika Deere
  • SVC-4871 - Votes: 3 - Script unable to llRequestURL() after crossing sim border - Ochi Wolfe
  • SVC-5504 - Votes: 3 - Avatar Scripts are counting on the land even when scripts in about land are disabled - Holger Gilruth
  • SVC-787 - Votes: 3 - llGetAgentInfo Returns AGENT_TYPING ONLY when Debug Setting playTypingAnim == TRUE - Ephemeral Rainbow
  • SVC-858 - Votes: 3 - llGetPrimitiveParams([PRIM_POINT_LIGHT]) on switched off light returns wrong parameters - Homer Horwitz
  • VWR-10639 - Votes: 3 - ALT-zoom on nametag focusses camera between avatar and original camera-position - Moon Metty

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/2010-05-24/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.