Bug triage/2009-06-15

From Second Life Wiki
Jump to: navigation, search



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


  • VWR-8841 - Votes: 19 - Memory usage goes to 2 gig, graphics frame rate tanks, crash dump taken, viewer not responding - Maggie Darwin
    • Fixed in 1.22.9 apparently but back in 1.23 builds. Last Linden action seems to be back when it was effecting 1.22.9 including the recorded last triage date. GW (T|C) -- 22:19, 14 June 2009 (UTC)

Hot by Vote

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

  • Lists populated, spines reticulated, hippos taken out for a walk. GW (T|C) -- 21:51, 14 June 2009 (UTC)
  • SVC-4378 added to fast track. GW (T|C) -- 21:56, 14 June 2009 (UTC)
  • VWR-8841 added to fast track listings. GW (T|C) -- 22:21, 14 June 2009 (UTC)
  • SVC-4378 - Votes: 10 - Change of permissions in inventory on recieved object grants Next Owner permissions - JoeTheCatboy Freelunch - Imported already

Resolved

  • batch resolve -- the usual culling of issues that have no recent updates, have been resolved, or are deleted/SEC. GW (T|C) -- 21:51, 14 June 2009 (UTC)

Transcript

Transcript is/will be at Bug triage/2009-06-15/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.