Bug triage/2007-08-20

From Second Life Wiki
Jump to navigation Jump to search


Next meeting: 2007-08-20 at 3pm. See Bug triage for details.

Fast Track Import

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

Hot by Vote

  • VWR-1907 - 9 votes - Attachments that do not take control of keys triggering release keys button to show up when attached. - CaptJosh Au
    • RESOLVE-Need Info (and add UI component)
  • SVC-553 - 8 votes - numerous reports of objects, notecards, scripts, gestures "missing from database" - Lex Neva
    • Aric to link to existing internal issue
  • VWR-1985 - 7 votes - Mandatory update - download loop - Sadako Shikami
    • RESOLVE-Need info. Waiting for reporter to try steps in comments.
  • SVC-507 - 7 votes - I can't login: "Unable to connect. Login packet never received by login server." - bicofino Voom
    • RESOLVE-Need info
  • VWR-2001 - 6 votes - objects "missing from database" - Jade Opel

Patches

Misc Pool

  • SVC-481 - 2 votes - permission sharing between scripts has been broken - Drew Dwi
    • RESOLVE/Cannot repro
  • SVC-82 - 2 votes - RAW files don't upload or download property lines in channel #4 - mathieu basiat
    • IMPORT
  • MISC-94 - 0 votes - Problem with video card X1950 - Dorian Bamaisin
    • RESOLVE/Need info
  • VWR-375 - 1 votes - The chat text window is unresponsive on G5 Mac - StarSong Bright
    • IMPORT (and assign to Aric)

Unfinished business

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

  • VWR-2142 - 11 votes - Non voice-enabled residents unable to switch off voice on their parcels - Edward Pearse

Resolved

Postponed

  • VWR-2010 - 7 votes - Blue dialogs now display in reversed order - Winter Ventura
    • Intended behavior with unintended side effects
    • possible solution might be the revamp the pop up system for random access--Boroondas Gupte 09:14, 20 August 2007 (PDT)
      • Putting on Tuesday agenda -- Rob Linden 09:44, 20 August 2007 (PDT)

Transcript

At the conclusion of this meeting, the transcript is/will be at Bug triage/2007-08-20/Transcript

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.