Difference between revisions of "Bug triage/2007-09-19"

From Second Life Wiki
Jump to navigation Jump to search
Line 37: Line 37:
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.
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 ===
=== Imported, New in RC 1.18.3.2 ===
* {{jira|VWR-2477}} - Votes: 0 - High memory usage after short periods of use in RC 1.18.3 - {{User|Funk Schnook}}
* {{jira|VWR-2443}} - Votes: 0 - framerate craters after cache loads.. friends and inventory fail to load.. specific to this release - {{User|rocky pickles}}
* {{jira|VWR-2483}} - Votes: 0 - the macviewer.xcodeprj file doesn't create stripped binaries on Deployment or Universal - {{User|Barney Boomslang}}


=== Resolved ===
=== Resolved ===

Revision as of 13:54, 17 September 2007


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)

Not new in RC 1.18.3, NOT Imported

Hot by Vote

Patches

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, New in RC 1.18.3.2

  • VWR-2477 - Votes: 0 - High memory usage after short periods of use in RC 1.18.3 - Funk Schnook
  • VWR-2443 - Votes: 0 - framerate craters after cache loads.. friends and inventory fail to load.. specific to this release - rocky pickles
  • VWR-2483 - Votes: 0 - the macviewer.xcodeprj file doesn't create stripped binaries on Deployment or Universal - Barney Boomslang

Resolved

Transcript

Transcript is/will be at Bug triage/2007-09-19/Transcript

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.