Bug triage/2009-11-23

From Second Life Wiki
Jump to: navigation, search



Next meeting: 2009-11-23 at 12:00 NOON 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

No issues over 10 votes

Misc Pool

Misc Pool

  • SVC-4706 - Votes: 1 - you take a prism and path cut it 0.500/1.000 then turn it aroudn to 0.000/0.500 that the prim gets darker - Gavin Ichigo
    • Imported
  • WEB-1383 - Votes: 8 - Profile images have moved beyond 2048 characters - Ken Gearhead
    • Imported
  • WEB-1384 - Votes: 2 - Profile Database http://world.secondlife.com/resident/ broken again - BlckCobra Shikami
    • Duplicate of above issue (WEB-1383)
  • VWR-16156 - Votes: 0 - Unstability when high graphics settings with a GEFORCE GTX 275 - AXLE Munro
    • Imported
  • SVC-4851 - Votes: 4 - llSensorRemove doesn't SEEM to work, passive state detected as active - Perry Mizin
    • Imported
  • WEB-1342 - Votes: 1 - Basic Account ticket only works when no email supplied in "Contact Email address" - Zai Lynch
    • Imported
  • WEB-1193 - Votes: 1 - region names not being escaped - SignpostMarv Martin
    • Imported
  • WEB-1183 - Votes: 1 - Sim owners unable to purchase sims ajoining to owned ones - Cummere Mayo
    • Resolved - Contact Support
  • WEB-1109 - Votes: 1 - Web browser differences on the Age Verification page - Furo Lane
  • WEB-1108 - Votes: 1 - XStreetSL forces user to use the language of their location instead of allowing them to select the language - BlckCobra Shikami
    • Imported
  • WEB-972 - Votes: 1 - Online form for age verification page does not update to allow users out side of US to enter correct information = this prevents age verification - Jayjay Seetan
    • Resolved - Needs more info
  • WEB-787 - Votes: 1 - Search appliance mis-reports group names with periods contained in the name. - SignpostMarv Martin
    • Imported
  • WEB-772 - Votes: 1 - Teen membership plans page (possibly) out of date - SignpostMarv Martin
    • Imported
  • WEB-538 - Votes: 1 - Land Store map very temperamental in Opera - Matthew Dowd
    • Resolved - Needs more info
  • WEB-467 - Votes: 1 - Data Mismanagement uncorrectable - Arawn Spitteler
    • Resolved - Expected Behavior
  • VWR-15851 - Votes: 1 - llAllowInventoryDrop(TRUE) on IMAGES on no-mod object fails (due SL still wants to apply texture to face) - Zak Kowalski
    • Resolved - Needs more info
  • VWR-15842 - Votes: 1 - Prim shift - Gray Keynes
    • Resolved - Needs more info
  • VWR-15825 - Votes: 1 - Second_Life_1-23-5-136262 Does not start with "old" versions of Visual C++ Redistributable Package - bitova loon
    • Imported
  • VWR-15820 - Votes: 1 - hover text does not fade out soon enough for megaprims - Doran Zemlja
    • Resolved - Needs more info
  • VWR-15725 - Votes: 1 - Crashes and Freezes with Macintosh Snow Leopard 10.6.1 - Possibly related to camera movement - pulseburst flow
    • Resolved - Needs more info

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-11-23/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.