Bug triage/2009-08-24

From Second Life Wiki
< Bug triage
Revision as of 21:09, 23 August 2009 by Harleen Gretzky (talk | contribs) (Added from Alexa's Monday PJIRA Triage filter - votes greater then 9 sorted by vote, priority - votes less then 10 sorted by priority, vote)
Jump to navigation Jump to search



Next meeting: 2009-08-24 at 12:00 NOON SLT at Hippotropolis Meeting area.. 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-14463 - Votes: 33 - Avatar clothing change invisible to all inworld, but visible to me. - Gracie Quartz - Last Triaged: 8/10/2009 12:00 PM
  • SVC-4739 - Votes: 21 - Sim freezes each time someone tp in or tp out, log in/log out - for a couple seconds untill new awatar arrives sim or leaves sim - Latexina Pinklady
  • SVC-343 - Votes: 10 - Control event not behaving as expected when 2 control scripts exist in the same object(prim) or linkset - Helena Lycia
  • VWR-13604 - Votes: 10 - "Report Abuse" makes UI backgrounds go transparent. - Ephyu Reino - Last Triaged: 6/3/2009 2:03 PM
  • VWR-14319 - Votes: 10 - Unsightly Stomach Seam (Vertex-lighting flaw) - uchi desmoulins

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/2009-08-24/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.