Bug triage/2007-10-01

From Second Life Wiki
Jump to: navigation, search


Next meeting: 2007-10-1 at 3:00 SLT in Hippotropolis. See Bug triage for details.

Fast Track Import

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

Patches

  • VWR-2600 - Votes: 3 - Add option to enable Full-Scene Anti-Aliasing (FSAA) in the viewer - Zorin Frobozz
    • Imported, assigned to WindLight team for consideration
  • VWR-2582 - Votes: 1 - Delete/Return crashes 1.18.3.5 Open Source built in VC Express 2005 using unmodified code - Nikki Claymore
    • Imported
  • VWR-2576 - Votes: 0 - Possible crash llselectmgr - Nicholaz Beresford
    • Imported
  • VWR-2524 - Votes: 1 - Possible crash on startup with group messages waiting (llnotify.cpp) - Nicholaz Beresford
    • Imported, noted Nicholaz's comment about VWR-2046 patch

Hot by Vote

  • WEB-340 - Votes: 24 - Website-based Friends Online list shows "no friends online" incorrectly - Coyote Pace
  • Imported, dupe?, assigned to Aric for investigation of dupe
  • VWR-2148 - Votes: 22 - Object Missing from Database - silas scarborough
    • Imported, assigned to Hamilton Linden
  • WEB-63 - Votes: 17 - 503 and other errors in forums - Ben Lineker
    • Imported, but resolved 'Fixed internally'
  • VWR-2530 - Votes: 16 - Says "initializing world" then freezes - Biggelsworthe Voom
    • Resolved 'needs more info'
  • VWR-2355 - Votes: 13 - Every minute crash, packet loss spikes - Elena Furse
    • Resolved 'needs more info'
  • SVC-483 - Votes: 12 - Script is missing from Database - Laronzo Fitzgerald
    • Resolved, duplicate of VWR-2148
  • VWR-2605 - Votes: 11 - Problem with the current fonts and cyrillic characters - Pesho Replacement
    • Resolved 'needs more info'
  • MISC-713 - Votes: 85 - Add "Return All Objects" as an estate-wide feature for a specified resident Autumnfox Vesperia
    • Imported, assigned to Benjamin Linden (Rx team)

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/2007-10-01/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.