Bug triage/2009-05-18

From Second Life Wiki
Jump to navigation Jump to search



Next meeting: 2009-05-18 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)

Patches

Patches

Hot by Vote

Monday PJIRA Triage Filter (votes over 10, imported removed)

  • - SVC-4253 - Votes: 22 - Estate tools showing wildly inaccurate script times - darling brody
    • Imported
  • - VWR-11420 - Votes: 14 - Objects/textures are removed from viewer memory too aggressively - dan linden - Last Triaged: 5/13/2009 8:39 AM
    • Imported
  • - SVC-3440 - Votes: 14 - llGetParcelFlags gives incorrect information - runay roussel
    • Imported
  • - VWR-13471 - Votes: 12 - llSetPrimitiveParams for fullbright true/false sporadically works & sticks - Angela Talamasca
    • Imported

Misc Pool

Monday PJIRA Triage Filter (votes under 10, imported removed)

  • - WEB-1106 - Votes: 1 - SL OpenID provider is whitelisting RPs - Eddy Stryker
    • Moved to Feature Request
  • - WEB-1096 - Votes: 0 - Xstreet is not crediting all accounts for L$ deposits made - Adaarye Shikami
    • Imported
  • - VWR-13512 - Votes: 9 - Texture upload is charged silently before successful upload, resulting in erroneous charge for failed texture upload - Marinedalek Tomorrow
    • Imported
  • - VWR-12476 - Votes: 5 - Voice Chat Failure - Seanas Alston
    • Resolved - Needs more information
  • - VWR-5559 - Votes: 5 - Viewer crashes with ATI Radeon HD 3650 GPU - Korgu Kidd
    • Resolved - Needs more information
  • - SVC-1669 - Votes: 4 - Estate tool top scripts should not show avatar attachments. - Daten Thielt
    • Resolved - Needs more information
  • - SVC-1731 - Votes: 4 - Unable to access Region from Teleport /LandMark or from logging into Second Life. Only flying in from an adjacent region works. - taradesh jewell
    • Resolved - Contact Support
  • - SVC-1738 - Votes: 4 - Grid Preformance Memory Leak - yukiko omegamu
    • Resolved - Duplicate of MISC-2329

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: 21 - Floating (Hover) Text penetrates walls - Ee Maculate
  • - VWR-1546 - Votes: 8 - Group Chat says only participant when there are other participants. - Rascal Ratelle - Last Triaged: 5/4/2009 3:12 PM
  • - VWR-8143 - Votes: 5 - Colored Spots on Objects and Avatars since the rolling restart on Friday the 11th of July - nelly janus

Transcript

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