Difference between revisions of "Bug triage/2008-03-19"

From Second Life Wiki
Jump to navigation Jump to search
Line 23: Line 23:
* {{jira|VWR-5463}} - Votes: 1 - Windlight causes graphics card degredation and eventually disables graphics card.  - {{User|Goldie Katsu}}
* {{jira|VWR-5463}} - Votes: 1 - Windlight causes graphics card degredation and eventually disables graphics card.  - {{User|Goldie Katsu}}
* {{jira|VWR-5555}} - Votes: 1 - Windlight largely incompatible with system - {{User|Arawn Spitteler}}
* {{jira|VWR-5555}} - Votes: 1 - Windlight largely incompatible with system - {{User|Arawn Spitteler}}
* {{jira|VWR-5525}} - Votes: 1 - 1.19.1 crashes on start up - {{User|wisdom aeon}}
* {{jira|VWR-5367}} - Votes: 0 - New video features (V19.1) are not fully supported in LSL - {{User|Garmin Kawaguichi}}
* {{jira|VWR-5367}} - Votes: 0 - New video features (V19.1) are not fully supported in LSL - {{User|Garmin Kawaguichi}}
* {{jira|VWR-5393}} - Votes: 0 - Right-click gesture activation spotty (gestures fail to show as activated when they are) - {{User|Yuu Nakamichi}}
* {{jira|VWR-5393}} - Votes: 0 - Right-click gesture activation spotty (gestures fail to show as activated when they are) - {{User|Yuu Nakamichi}}

Revision as of 17:20, 18 March 2008


Next meeting: 2008-03-19 at 3pm PST at Bridie Linden's house.

Import?

(Bugs reported in 1.19.1 RC1 — consider for import?, sorted by votes)

Fast Track Import =

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

Hot by Vote

High Voted Bugs

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-5496 - Votes: 8 - Crashes from keyboard input at various places in the user interface - Raloc Dorado

Resolved

  • VWR-5448 - Votes: 3 - When typing in IM window, something redirects the cursor elsewhere, so it becomes like a fight to keep the curser in the IM window long enough to complete the sentence each time - Sterling Ronzoni
    • Resolved as dupe of VWR-5475 (already imported)
  • VWR-5639 - Votes: 2 - crash on inventory refresh - Tayra Dagostino
    • Resolved, dupe of VWR-5382
  • VWR-5533 - Votes: 1 - Crash Logs Do Not Send. - Meghan Dench
    • Resolved, Fix Pending

Transcript

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