Difference between revisions of "Bug triage/2009-06-01"

From Second Life Wiki
Jump to navigation Jump to search
(→‎Misc Pool: rm vwr-2726, already on the hot by vote list)
(→‎Misc Pool: rm svc-2306 as an overly vague rant by a known JIRA griefer, rm vwr-7814, misfiled issue that needs to be taken up with hippo)
Line 43: Line 43:
* {{jira|VWR-8414}} - Votes: 0 - When using the new skin, anoying graphics pop up when using other things outside of SL - {{User|Raz01 Razor}}
* {{jira|VWR-8414}} - Votes: 0 - When using the new skin, anoying graphics pop up when using other things outside of SL - {{User|Raz01 Razor}}
* {{jira|VWR-7270}} - Votes: 0 - Creating a new inventory folder while searching filter is applied renames the current selected folder instead. - {{User|Vittorio Beerbaum}}
* {{jira|VWR-7270}} - Votes: 0 - Creating a new inventory folder while searching filter is applied renames the current selected folder instead. - {{User|Vittorio Beerbaum}}
* {{jira|VWR-7814}} - Votes: 0 - No IM Chat alert or HUD alerts from Hippo - {{User|Barrett Slade}}
* {{jira|SVC-2306}} - Votes: 0 - Constant server-side issues... trackable - {{User|eren padar}}
* {{jira|SVC-1897}} - Votes: 0 - Child prims stop responding to size and position changes - {{User|Rifkin Habsburg}}
* {{jira|SVC-1897}} - Votes: 0 - Child prims stop responding to size and position changes - {{User|Rifkin Habsburg}}



Revision as of 14:42, 30 May 2009



Next meeting: 2009-06-01 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

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-06-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.