Difference between revisions of "Bug triage/2009-03-16"

From Second Life Wiki
Jump to navigation Jump to search
(Moved SVC-3182 and VWR-8374 to resolved section)
Line 36: Line 36:
* {{jira|VWR-2775}} - Votes: 1 - Unpredicatable crashes in Linux-client since version 1.18.3.5 (1.18.3.4 was ok) - {{User|Marcoh Larsen}}
* {{jira|VWR-2775}} - Votes: 1 - Unpredicatable crashes in Linux-client since version 1.18.3.5 (1.18.3.4 was ok) - {{User|Marcoh Larsen}}
* {{jira|VWR-11930}} - Votes: 0 - Teleporting either Disconnects or Crashes SL - {{User|Flurry Parx}}
* {{jira|VWR-11930}} - Votes: 0 - Teleporting either Disconnects or Crashes SL - {{User|Flurry Parx}}
* {{jira|VWR-8374}} - Votes: 0 - bandwidth indicator does not fit - {{User|wulfric chevalier}}
* {{jira|SVC-3890}} - Votes: 0 - texturechange scripts refuse to work in class4 sims - {{User|Yuukie Onmura}}
* {{jira|SVC-3890}} - Votes: 0 - texturechange scripts refuse to work in class4 sims - {{User|Yuukie Onmura}}
* {{jira|VWR-11931}} - Votes: 0 - Video stream broken on linux - {{User|Tayra Dagostino}}
* {{jira|VWR-11931}} - Votes: 0 - Video stream broken on linux - {{User|Tayra Dagostino}}
Line 70: Line 68:
* {{jira|SVC-3182}} - Votes: 0 - Payment received by one vendor ended up in another avatar's transaction history - {{User|Timeless Prototype}}
* {{jira|SVC-3182}} - Votes: 0 - Payment received by one vendor ended up in another avatar's transaction history - {{User|Timeless Prototype}}
** Moved to SEC-190 --[[User:Harleen Gretzky|Harleen Gretzky]] 05:59, 16 March 2009 (UTC)
** Moved to SEC-190 --[[User:Harleen Gretzky|Harleen Gretzky]] 05:59, 16 March 2009 (UTC)
* {{jira|VWR-8374}} - Votes: 0 - bandwidth indicator does not fit - {{User|wulfric chevalier}}
** Already resolved as NMI --[[User:Harleen Gretzky|Harleen Gretzky]] 06:03, 16 March 2009 (UTC)


== Transcript ==
== Transcript ==

Revision as of 23:03, 15 March 2009



Next meeting: 2009-03-16 at 12:00 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

  • VWR-12427 - Votes: 0 - A non-ASCII character in boost header file makes viewer build to fail on non-US versions of Windows - Alissa Sabre
  • VWR-12385 - Votes: 0 - Building hotkeys to include next/previous prim in a link set - Techwolf Lupindo

Misc Pool

Misc Pool

  • WEB-989 - Votes: 1 - Blog illogically requires secure connection to view rather than just to login and comment - Gordon Wendt

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

  • VWR-755 - Votes: 18 - Floating (Hover) Text penetrates walls - Ee Maculate
    • As designed but left open by Linden for votes. GW (T|C) -- 22:46, 15 March 2009 (UTC)
  • WEB-982 - Votes: 15 - Problems for blogs.secondlife.com - Argent Stonecutter
    • Accordint to comments seems to be a non LL issue so nothing to triage. GW (T|C) -- 22:46, 15 March 2009 (UTC)
  • SVC-3182 - Votes: 0 - Payment received by one vendor ended up in another avatar's transaction history - Timeless Prototype
  • VWR-8374 - Votes: 0 - bandwidth indicator does not fit - wulfric chevalier

Transcript

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