Bug triage/2008-01-21

From Second Life Wiki
Jump to navigation Jump to search


Next meeting: 2007-XX-XX at TIME and PLACE (FIXME). 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

High Voted Bugs

  • VWR-2950 - Votes: 14 - Group Notices and Group IMs Constantly Malfunctioning - wayfinder wishbringer
    • Leaving as is for now
    • IM improvements in the dev pipeline — let's wait and see how these help!
  • SVC-1061 - Votes: 23 - Some link sets spontaneously unlink when taken and rezzed - Lex Neva
    • Imported for QA to try and repro
  • VWR-2364 - Votes: 19 - NVIDIA GEFORCE7900GTX -updated or new drivers since 94.24 cause graphics issues with prim displays - SunShine Kukulcan
    • Imported after comment from Untameable Wildcat
  • VWR-954 - Votes: 11 - Objects flash changing every texture I have....sometimes all trees, sometimes walls, sometimes avatars...never know what. - lauren weyland
    • Imported
  • VWR-3021 - Votes: 13 - Random and frequent crashes - Leanne Karas
    • Imported but waiting for more info

Patches

Patches

  • VWR-3093 - Votes: 13 - Allow MU* (MUCK, MUSH, MUX, MUD) like ""poses"" (=IRC emotes) in chat and IMs. - Henri Beauchamp
    • Imported
  • VWR-4263 - Votes: 1 - Chinese (Simplified) Translations for Preference floaters for WindLight - Geneko Nemeth
    • Imported
  • SVC-1229 - Votes: 0 - return_first_event takes the wrong type - Strife Onizuka
    • Imported, assigned to Soft
  • SVC-1210 - Votes: 1 - state_exit: LSL compiler should disallow state transition calls. - Vex Streeter
    • Imported
  • VWR-3749 - Votes: 0 - Windlight linkage fails on standalone build due to no boost_regex linkage - Michelle2 Zenovka
    • Tofu Linden already on it!

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-01-21/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.