Bug triage/Wednesday Agenda

From Second Life Wiki
Jump to navigation Jump to search

Next meeting: 2010-05-19 at 2.00 PM PDT at Bambers' Office at Denby. See Bug triage for details.

Fast Track Import

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

Misc Pool

Misc Pool


  • VWR-19918 - 42 votes - Scripted objects used in previous inworld sessions appear in lower notifications bar after relogin and accumulate over further logins - nyll bergbahn
  • VWR-19830 - 15 votes - Unable to rename inventory items including scripts and notecards and Land-Marks - Lara Nguya
  • VWR-19774 - 15 votes - You can not group outfits by category by creating folders and dropping outfits into these. - Luc Starsider
  • VWR-20183 - 9 votes - RenderVolumeLODFactor is set at '0' as default for low graphics in Viewer 2.1 - causes malformed circular prims and unresolved sculpties - Hitomi Tiponi
  • VWR-19951 - 8 votes - ScriptDialog Notification of objects hidden, when multiple arrive on same object, and persisted, reappearing on relog - Thomas Shikami
  • VWR-19846 - 7 votes - Opening the sidebar shrinks a wide chat text window, but closing doesn't restore it - Kidd Krasner

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/2010-05-19/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.