Bug triage/2008-05-21

From Second Life Wiki
< Bug triage
Revision as of 09:54, 28 May 2008 by Bridie Linden (talk | contribs) (Bug triage/Wednesday Agenda moved to Bug triage/2008-05-21)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Next meeting: 2008-05-21 at 3pm PST at Bridie Linden's house.


(Bugs reported in 1.20 Release Candidate — consider for import?, sorted by votes)

  • VWR-7174 - Votes: 3 - Glow PROBLEM behind transparent surface - Naiman Broome
    • Imported - Assigned to Pastrami Linden
  • VWR-7251 - Votes: 3 - Poor performance relative to released (1.19.1(4)) viewer - Cynebald Ceawlin
    • Won't Fix
  • VWR-6597 - Votes: 2 - Can't save texture memory size in preference-hardware - maverick offcourse
    • Imported - Assigned to Zen Linden
  • VWR-6699 - Votes: 2 - Shaders are disabled on supported video card - Deany Fall
    • Imported - Assigned to Zen Linden
  • VWR-6740 - Votes: 2 - SpaceNavigator input cross-talk to other apps - Whichway Janus
    • Attached to Meta issue VWR-6363
  • VWR-6889 - Votes: 2 - Unable to leave group when role has no allowed abilities - Geraldine Giha
    • Imported - Assigned to Triage
  • VWR-6848 - Votes: 2 - Space Navigator does not function when other game controller device is already known by Windows - Ronald Richez
    • Attached to Meta issue VWR-6363
  • VWR-7131 - Votes: 2 - Special layers are not rendered through Windlight water. - Argent Stonecutter
    • Imported - Assigned to Pastrami Linden
  • VWR-6833 - Votes: 2 - 1.20.3 Crash on Login/During Essential InWorld Activitys - Kitty Hirsch
    • Asked reporter to install lastest RC and see if they are still having the problem
  • VWR-6501 - Votes: 2 - Objects rotate wildly in edit mode with 3dconnexion Space Navigator plugged in - Hypatia Callisto
    • Attached to Meta issue VWR-6363
  • VWR-7144 - Votes: 2 - Camera behavior erratic in edit mode - Lindal Kidd
    • Imported - Assigned to Bridie Linden
  • VWR-6984 - Votes: 2 - Corrupt fonts - Michelle2 Zenovka
    • Tofu is researching
  • VWR-7119 - Votes: 2 - When using Space Navigator, grid does not work, snaps do not work. - windyweather vanalten
    • Attached to Meta issue VWR-6363
  • VWR-6016 - Votes: 1 - FMOD problem: update3dPosition error - Tayra Dagostino
    • Imported - Assigned to Triage
  • VWR-6246 - Votes: 1 - All Menu items seem to be disabled, and right clicking anywhere in world causes a jump, not a Pie Menu. - Robin Sojourner
    • Asked reporter to install latest RC
  • VWR-6252 - Votes: 1 - Alerts and Notifications on new UI need more contrast or color. - rena kuhn
    • Resolved - Duplicate
  • VWR-6300 - Votes: 1 - RC outputs wrong value type when importing from settings.xml - Kitty Barnett
    • Resolved - Duplicate
  • VWR-6388 - Votes: 1 - Corrupted Verticies - Zion Tristan
    • Told reported to update drivers

Fast Track Import

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

Hot by Vote

High Voted Bugs



Misc Pool

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.




Transcript is/will be at Bug triage/2008-05-21/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.