Difference between revisions of "Bug triage/2008-04-14"

From Second Life Wiki
Jump to navigation Jump to search
Line 12: Line 12:
* {{jira|VWR-6301}} - Votes: 54 - Pulsating/glowing/fading outlines when building. Is this absolutely neccessary?? HELL when building for hours in RC 1.20!!! - {{User|Michi Lumin}}
* {{jira|VWR-6301}} - Votes: 54 - Pulsating/glowing/fading outlines when building. Is this absolutely neccessary?? HELL when building for hours in RC 1.20!!! - {{User|Michi Lumin}}
** {{jira|VWR-6301}} possibly a duplicate of {{jira|VWR-6244}}
** {{jira|VWR-6301}} possibly a duplicate of {{jira|VWR-6244}}
* {{jira|SVC-688}} - Votes: 23 - Scripted email failing from certain objects - {{User|Escort DeFarge}}
* {{jira|SVC-688}} - Votes: 24 - Scripted email failing from certain objects - {{User|Escort DeFarge}}
* {{jira|VWR-6259}} - Votes: 16 - SLURL and secondlife:// links open a second SL viewer - {{User|Royanna McCallen}}
* {{jira|VWR-6259}} - Votes: 16 - SLURL and secondlife:// links open a second SL viewer - {{User|Royanna McCallen}}
* {{jira|SVC-2093}} - Votes: 21 - Community Gateway Wien has high physics load since havok 4 - newbies deployed into a laggy situation - {{User|ice stawberry}}
* {{jira|SVC-2093}} - Votes: 21 - Community Gateway Wien has high physics load since havok 4 - newbies deployed into a laggy situation - {{User|ice stawberry}}
Line 56: Line 56:
* {{jira|VWR-5857}} - Votes: 0 - ""Start/Stop Movie to Disk""  Doesn't make a movie - {{User|Angelina Sinclair}}
* {{jira|VWR-5857}} - Votes: 0 - ""Start/Stop Movie to Disk""  Doesn't make a movie - {{User|Angelina Sinclair}}
* {{jira|EVT-16}} - Votes: 0 - Pulling a Microsoft over run error when only buying 16m lots - {{User|Chocolate Martini}}
* {{jira|EVT-16}} - Votes: 0 - Pulling a Microsoft over run error when only buying 16m lots - {{User|Chocolate Martini}}
* {{jira|VWR-5111}} - Votes: 5 - Camera panning problem - random camera movements - {{User|timmie124 Tone}}


== Pre-meeting activity ==
== Pre-meeting activity ==

Revision as of 11:42, 14 April 2008


Next meeting: 2008-04-14 at 12 PM 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)

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

Resolved

Transcript

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