Difference between revisions of "Bug triage/2009-02-02"

From Second Life Wiki
Jump to navigation Jump to search
Line 19: Line 19:
* {{jira|SVC-3435}} - Votes: 16 - Start outfit (a.k.a. default Avatar) isn't always full-perm for new residents. - {{User|Boroondas Gupte}}
* {{jira|SVC-3435}} - Votes: 16 - Start outfit (a.k.a. default Avatar) isn't always full-perm for new residents. - {{User|Boroondas Gupte}}
* {{jira|VWR-5708}} - Votes: 13 - Incorrect handling of /proc/cpuinfo in libvivoxsdk.so. - {{User|Xaden Kjeller}}
* {{jira|VWR-5708}} - Votes: 13 - Incorrect handling of /proc/cpuinfo in libvivoxsdk.so. - {{User|Xaden Kjeller}}
* {{jira|VWR-5530}} - Votes: 14 - Minimized windows not remembering position - {{User|Shirley Marquezn}} - patch attached
* {{jira|VWR-5530}} - Votes: 14 - Minimized windows not remembering position - {{User|Shirley Marquezn}} - patch attached - "fix pending" since 4 months
* {{jira|VWR-11697}} - Votes: 14 - Jumping Halts Strafing Movement - {{User|Myoukitsune Kirkorian}}
* {{jira|VWR-11697}} - Votes: 14 - Jumping Halts Strafing Movement - {{User|Myoukitsune Kirkorian}}
* {{jira|VWR-9558}} - Votes: 12 - difficulties with teleporting for a few days now ...unable to complete your teleport request in a timely fashion - {{User|luna fratica}}
* {{jira|VWR-9558}} - Votes: 12 - difficulties with teleporting for a few days now ...unable to complete your teleport request in a timely fashion - {{User|luna fratica}}

Revision as of 06:42, 2 February 2009



Next meeting: 2009-02-02 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

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

  • 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
    • already resolved as NMI should not have shown --Harleen Gretzky 05:32, 2 February 2009 (UTC)
  • VWR-3044 - Votes: 0 - 1.18.4 (3): Zooming out 5-6x with CTL-8 causes all graphics to stretch, making in-world look like hyperspace. Zooming out one more time makes the screen go black - Kaden Harbour

Transcript

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