Bug triage/2009-01-05

From Second Life Wiki
< Bug triage
Revision as of 11:36, 6 January 2009 by Alexa Linden (talk | contribs) (→‎Misc Pool)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search



Next meeting: 2009-01-05 at 12:00 PM SLT at Hippotropolis Meeting area🖈. See Bug triage for details.

Fast Track Import

Hot by Vote

High Voted Bugs

  • VWR-721 - Votes: 16 - Dates are not displayed in the local date format - Jon Meriman - New patch attached
    • Imported
  • VWR-5287 - Votes: 12 - Prims turning Phantom on their own - stacyanne homewood
    • Resolved - Needs more info
  • VWR-6807 - Votes: 11 - Glow not working in 1.20 - dimentox travanti
    • Resolved - Needs more info
  • VWR-9763 - Votes: 11 - Poor Performance with ATI 4850 video card - increases when all textures are loaded?!?! - fazer gynoid
    • Resolved - Needs more info

Patches

Patches

  • VWR-11310 - Votes: 0 - Use LZMA compression for precompiled libraries and linux release packages. - Khyota Wulluf
    • Triaged date added

Misc Pool

Misc Pool

  • VWR-11341 - Votes: 1 - Selecting a prim inside another prim impossible - Tetsuryu Vlodovic
    • Imported
  • VWR-6191 - Votes: 0 - Hyperlinks not launching for residents using MouseKeys - DJQuad Radio
    • Resolved - Need more info
  • SVC-2175 - Votes: 0 - physical vehicles stop responding to scripts until region restart - paulie Femto
    • Resolved - Need more info
  • VWR-8314 - Votes: 0 - scroll down error in Advanced>Clothing>Wear - Sigma Avro
    • Imported
  • VWR-3486 - Votes: 0 - File folder not seen in object texture edit file folders - Barrett Slade
    • Resolved - Need more info
  • VWR-3461 - Votes: 0 - can't have both shinnyness and atmospheric shaders enabled without glitching the graphics (WL of course) - TigroSpottystripes Katsu
    • Resolved - Need more info
  • VWR-3454 - Votes: 1 - Opening menus using the ALT key - ZigZag Freenote
    • Move to Feature Request
  • VWR-3451 - Votes: 0 - CTRL-Backspace should delete word left - ZigZag Freenote
    • Move to Feature Request
  • VWR-3430 - Votes: 0 - errors trying to upload texture or animations or sounds into game - sweet valentine
    • Resolved - Need more info
  • VWR-6087 - Votes: 0 - Land Textures render improperly, and randomly change - Chaos Mohr
    • Resolved 0 Duplicate of VWR-10963
  • VWR-8505 - Votes: 0 - Changing Antialiasing from x4 to x8 causes odd graphics error - Jason Swain
    • Imported
  • VWR-3376 - Votes: 1 - Failed login advances progress bar's start position - ZigZag Freenote
    • Description of issue added - Imported

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/2009-01-05/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.