Bug triage/2008-03-05

From Second Life Wiki
Jump to navigation Jump to search


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

Import?

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

  • VWR-5207 - Votes: 3 - Sculpted Prims Load/Look Different in v1.19 than in v1.18 or Lower - Earalia Nolan
    • Imported
  • VWR-5284 - Votes: 3 - DNS Could not resolve host name error after upgrading to 1.19.0.4 - Evangeline Wind
    • Left open
  • VWR-5158 - Votes: 1 - SL Freezes, Can't Walk after 30 secs - edmundtyler blackadder
    • Resolved, Contact Support
  • VWR-5208 - Votes: 2 - Voice IM volume slider being moved by unrelated dialog open/close actions in 1.19.x Dazzle and now Release versions - Worsethe Dayafter
    • Imported
  • VWR-5203 - Votes: 1 - when resizing a newly created prim - texture repeat numbers change on their own - corrupt cache - Renee Faulds
    • Resolved, can't repro
  • VWR-5202 - Votes: 0 - SecondLife keeps crashing after logging in. - Helo Kirax
    • Resolved, Needs More Info
  • VWR-5209 - Votes: 0 - LSL - running checkbox is sometimes greyed out in scripts - Snugly Littlething
    • Resolved, Needs More Info
  • VWR-5260 - Votes: 0 - was logged off for being idle although I clearly wasn't - Manutolkanokis Islander
    • Left open, last triage date added
  • VWR-5268 - Votes: 0 - Gestures limitation varies - Toby Marjeta
    • Resolved, Won't Finish (see Torley's comment)

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-03-05/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.