Bug triage/2007-11-19

From Second Life Wiki
Jump to navigation Jump to search

Next meeting: 2007-11-19 at Monday, 12pm PST at the Hippotropolis Meeting area


This one isn't a top voted feature (yet), but between the bug and associated feature, it's near the top. Gigs Taggart
  • SVC-913 - Votes: 69 - Allow LSL scripts to act as HTTP servers in order to replace XMLRPC with something scalable - Sean Linden
    • Imported - Assigned to Sean Linden
  • SVC-29 - Votes: 94 - XMLRPC sporadically (but usually) very slow - Apotheus Silverman
    • If a resident will send an email to the SL Dev team, Rob Linden will follow up.
  • WEB-382 - Votes: 2 - Bugs and Proposals on the JIRA Cannot Be Closed or Moved Without Author Consent - Prokofy Neva
    • Closed - Needs more info
  • VWR-3071 - Votes: 1 - Objects Set for Sale should not default to "Show in Search" - Prokofy Neva
    • Imported - Assigned to Rob Linden

Ping on VWR-442

    • In review as of this posting

Fast Track Import

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

  • WEB-383 - Votes: 0 - membership plans page is out of date - Gigs Taggart
    • Imported - Assigned to Jeff Linden

Hot by Vote

  • WEB-380 - Votes: 11 - "Fixed Internally" should not appear as "Resolved" in JIRA; voting should continue - Ordinal Malaprop
    • Imported - Assigned to Rob Linden
  • MISC-488 - Votes: 12 - rez objects only works if i'm online - october brotherhood
    • Changed to SVC
    • Imported - Assigned to Aric Linden


  • VWR-3272 - Votes: 3 - Shader support removed in Windlight for some cards that work well (when it is re-enabled) - Abyssin Otoro
    • Imported - Assigned to Windlight Team
  • VWR-3265 - Votes: 0 - IM Tabs stack vertical rather than horizontal (Yet another solution to the communicate window) - Matthew Dowd
    • Imported - Assigned to RX Team
  • VWR-1549 - Votes: 7 - Move Friends and Groups tabs from left to bottom - Matthew Dowd
    • Imported - Assigned to RX Team

Misc Pool

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.



  • VWR-3004 - Votes: 13 - random crashes on recent linux clients - tx Oh
A little vague, and original reporter and others have reported lower levels of crashing now Gigs Taggart


Transcript is/will be at Bug Triage/2007-11-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.