Bug triage/2010-03-29

From Second Life Wiki
Jump to: navigation, search



Next meeting: 2010-03-29 at 12:00 NOON PDT 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)

  • Solid repros
  • SVC-5511 - 0 Votes - llTakeControls Traps repeating event when controls are changed or permission revoked - Void Singer
    • Imported
  • VWR-16872 - 2 Votes - Build Tools: Local Ruler Rotation is Inconsistent - Void Singer
    • Imported
  • SVC-4518 - 0 Votes - Hollow Shape Setting Reverts To Default on Hollow Percentage 0.0 - Void Singer
    • Moved to Feature Request
  • VWR-14555 - 0 Votes - taking an object to inventory (inconsistently) replaces a null description "" with "(No Description)" - Void Singer
    • Imported

Hot by Vote

High Voted Bugs

Misc Pool

Misc Pool

  • VWR-18280 - Votes: 1 - Support for ATI Radeon HD 5800 Series - Maelstrom Flasheart
    • Imported
  • SVC-5251 - Votes: 0 - Offline messages not being sent to email - Kurt Mortensen
    • Resolved - Needs more info
  • SVC-5509 - Votes: 0 - llRezObject causes old prims on parcel to be returned - Virii Mode
    • Resolved - Needs more info
  • VWR-18387 - Votes: 0 - Rotation calc: no high divide numbers possible (update: and wrong tex rot) - Heron Halberstadt
    • Resolved - Needs more info
  • MISC-4063 - Votes: 4 - ToS: The text of section 2.2 of the ToS needs changing to reflect the fact that teens and adults are now sharing the official forums. - spinster Voom
  • VWR-9037 - Votes: 2 - Failure to Load Gestures bottlenecking inventory downloading - Ashlin McMahon
    • Imported
  • SVC-4491 - Votes: 5 - One-second delay on llCreateLink is excessive - Dale Innis
    • Imported
  • SVC-1126 - Votes: 4 - llEmail() causes mails to be sent with no body - sasun steinbeck
    • Imported
  • SVC-1139 - Votes: 4 - Phantom Physics Bug: Physical objects are seperated by an invisible barrier, cannot directly touch or rest on surfaces - Neotoy Story
    • resolved - Expected Behavior
  • SVC-1759 - Votes: 4 - llGetAnimation constant transparency - Strife Onizuka
    • Imported
  • SVC-3510 - Votes: 4 - LINK_* flags do not work with llBreakLink - Strife Onizuka
    • Imported
  • VWR-10713 - Votes: 4 - Inventory jumps on friend's login/logout - Silver Key
    • Imported
  • VWR-11418 - Votes: 4 - Textures in 1.21.6 don't load even after clicking them - dan linden
    • Last Triaged date added
  • VWR-14603 - Votes: 4 - shadow enabled high-res snapshots get total black - Dil Spitz
    • Resolved - Needs more info
  • VWR-739 - Votes: 4 - Client->Rendering->Types->Character (CTRL-ALT-SHIFT-4) does not function properly - Harleen Gretzky
    • Imported
  • WEB-1323 - Votes: 4 - """Ran Alert Lock old Closed tickets"" generates confusing email to submitter" - Qie Niangao
    • Imported
  • MISC-2623 - Votes: 3 - Muted residents can continue to communicate and harrass via the SL Exchange (XStreet) message system - Charity Colville
    • Imported
  • MISC-2710 - Votes: 3 - Help Island Public Neglect - Dirk Talamasca
    • Imported
  • SVC-1546 - Votes: 3 - different unsit behavior - Gypsy Paz
    • 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/2010-03-29/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.