Bug triage/2008-12-22

From Second Life Wiki
< Bug triage
Revision as of 20:05, 21 December 2008 by Gordon Wendt (talk | contribs) (→‎Misc Pool: rm SVC-209 as a dupe)
Jump to navigation Jump to search


Next meeting: 2008-12-22 at 12:00PM 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-10971 - Votes: 0 - Frame rate (FPS) changes wildly with VBO enabled on an ATi Radeon 2900 XT - Net Antwerp
    • Triaged on 12-15-08 but relegated due to confusion on whether this setting was on by default, clarified in issue comments and issue reopened so fast tracking. GW (T|C) -- 03:18, 16 December 2008 (UTC)

Hot by Vote

High Voted Bugs

  • SVC-3530 - Votes: 29 - HTTP Transfer Data Failure on Region Handoff - Suzanna Soyinka
  • SVC-3556 - Votes: 12 - Intra-Region teleport not possible when region is full - Chalice Yao
  • VWR-7204 - Votes: 12 - Loading time of sculpts - Naiman Broome
  • SVC-3543 - Votes: 11 - Estate Tools & llTeleportAgentHome - Users with invalid homepoints are not removed from the sim, even when estate banned. - Drew Dwi

Patches

Patches

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

  • VWR-10971 - Votes: 0 - Frame rate (FPS) changes wildly with VBO enabled on an ATi Radeon 2900 XT - Net Antwerp
    • Triaged on 12-15-08 but relegated due to confusion on whether this setting was on by default, clarified in issue comments and issue reopened so fast tracking. GW (T|C) -- 03:19, 16 December 2008 (UTC)

Resolved

  • VWR-5287 - Votes: 12 - Prims turning Phantom on their own - stacyanne homewood
    • Re-occuring listing, no repro given since request for one after last time this was triaged. GW (T|C) -- 00:21, 21 December 2008 (UTC)
      • Resolved as needs more info while awaiting that repro which will keep it off the lists until reopened with a repro. GW (T|C) -- 00:24, 21 December 2008 (UTC)
  • VWR-10311 - Votes: 2 - Enable LipSync by default - Mm Alder
    • Feature request and as such shouldn't be on the bug triage lists. GW (T|C) -- 00:26, 21 December 2008 (UTC)
  • VWR-3511 - Votes: 2 - Very strange spanish translations - Dale Glass
    • Old issue, no recent updates. GW (T|C) -- 03:57, 22 December 2008 (UTC)

Transcript

Transcript is/will be at Bug triage/2008-12-22/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.