Bug triage/2009-05-13

From Second Life Wiki
Jump to navigation Jump to search

Next meeting: 2009-05-13 at 2:00 PM SLT at Bambers' Office at Denby. See Bug triage for details.

1.23 RC/PN by vote

  • VWR-13355 - 11 votes - Avatar eyes are rendered incorrectly metallic with shadows enabled in 1.23 RC - Miriel Enfield
    • Imported
  • VWR-13316 - 9 votes - Cant copy an attached item to another folder of my inventory. Need this feature back, cause if somebody edit an attached item and do a mistake, you need to copy the attachment for rescue it back. - Larissa Vacano
    • Last Triaged date added
  • VWR-13416 - 7 votes - The Center of Rotation changes location and orientation after linking a set of prims, then deselecting/reselection the linkset - Ethos Erlanger
    • Imported
  • VWR-5361 - 6 votes - Attachments of Group Notices can't be opened or saved from all the Blue Dialog PopUps of waiting notices at log in - Just the first one opened - zinbaco kattun
    • Imported
  • VWR-11420 - 6 votes - Objects are removed from viewer memory too aggressively - dan linden
    • Last Triaged date added
  • VWR-13361 - 5 votes - Graphical Glitch on Avatar Chest - Nichole Fadoodle
    • Resolved - Needs more info
  • VWR-4601 - 4 votes - Windlight: SL window in background displays huge, washed-out versions of windows in foreground - Gellan Glenelg
    • Imported
  • VWR-10112 - 4 votes - Regularly, but intermittently, being logged out... - Vicky Jayaram
    • Imported
  • VWR-12933 - 4 votes - After Login Textures take a long time to Load. - MAtto Destiny
    • Imported
  • VWR-13137 - 4 votes - invisible avatar - Arizona Davies
    • Last Triaged date added
  • VWR-13340 - 4 votes - "normal" Alpha prims have the properties of an invisiprim ( minus the cutting of the mesh ) - Kaine Lowenstark
    • Last Triaged date added
  • VWR-13105 - 3 votes - Restore to Last Position can lead to inventory loss when triggered by mistake. - Thickbrick Sleaford
    • Imported

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.



-- Duplicate and resolved by Garn as such. ~CM

-- resolved as duplicate of SVC-2766 ~CM

--Resolved as dulicate of SVC-2766 and VWR-13382 ~CM


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