Bug triage/2008-05-07

From Second Life Wiki
Jump to: navigation, search


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

Import?

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

  • VWR-6784 - Votes: 12 - Viewer issue with 1.20 viewer. No matter if using Secondlife Client 1.20 or open sourced, avatar's system eyelashes appear clotted. Alpha aspects not working; skin types/body shapes/ make no difference - Lilibeth Andree
    • Imported - Assigned to Pastrami Linden
  • VWR-6942 - Votes: 12 - Avatar Renders Black when Anti Aliasing enabled in RC 1.20 - Vivienne Schell
    • Imported - Assigned to Pastrami Linden
  • VWR-7031 - Votes: 11 - Version 1.20 RC5 Possible memory leak on graphics. When turning too quickly SL locks or crashes. Graphics will load slow, not properly, lag you very much - Mallory Taov
    • Marked with Triage date
  • VWR-6604 - Votes: 10 - Avatar shape changed proportions in RC version - Guilhermo Beck
    • Duplicate
  • VWR-6897 - Votes: 8 - 1.20 RC4, Mac Version: extremely high disk usage - Darko McMahon
    • Imported - Assigned to Triage
  • VWR-6828 - Votes: 8 - Character > Show Look At / Show Point At don't work - Hachiro Yokosuka
    • Imported - Assigned to Triage
  • VWR-6847 - Votes: 6 - Joystick Setup / Settings are not preserved between client sessions - Zorin Frobozz
    • Fixed Pending
  • VWR-6865 - Votes: 5 - Terrain texture not loading properly (only displaying high/4th ground texture) - Vixen Fairplay
    • Linked to internal issue DEV-14313
  • VWR-6226 - Votes: 4 - Editting a single llinked prim and moving that prim, then undoing the move to that single prim will return the prim to its previous location but also move the entire linked set the same distance X, Y or Z - Tindallia Soothsayer
    • Imported - Assigned to Triage
  • VWR-6707 - Votes: 4 - 1.20 - Crash on Login/Frequent Crashing - Lazure Ryba
    • Marked with Triage date
  • VWR-6658 - Votes: 3 - X, Y, Z alignment lines when editing a prim no longer accurately display spacial position - Khashai Steinbeck
    • Fixed
  • VWR-6912 - Votes: 3 - Mac Pro / multicore - one core rises to 100% causing temporary freeze - Court Goodman

Fast Track Import

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

Hot by Vote

High Voted Bugs

Patches

Patches

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.

Imported

Resolved

Transcript

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

<perl>

  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";

}


</perl>

  • Pick a reasonable cutoff point, and copy the output into the appropriate section of your newly created page.