Bug triage/2007-10-10

From Second Life Wiki
< Bug triage
Revision as of 09:23, 15 October 2007 by Torley Linden (talk | contribs) (New page: {{Bug triage}} Next meeting: 2007-10-17 at 3pm at [http://slurl.com/secondlife/Levenhall/152/40/30 Bridie's Place] in Linden Village. Aric and Torley are guest-hosting while Bridie is "Ou...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


Next meeting: 2007-10-17 at 3pm at Bridie's Place in Linden Village. Aric and Torley are guest-hosting while Bridie is "Out Of Office". See Bug triage for details.

Fast Track Import

(Move bugs here that have solid repros, or valid patches that you have reviewed)

New in 1.18.3.5 or RC 1.18.3?, NOT Imported

  • VWR-2565 - Votes: 6 - Lag and very low framerates on an otherwise healthy system - Doris Haller
    • ALREADY IMPORTED
  • VWR-2628 - Votes: 0 - crash in operator*(LLVector3 const&, LLQuaternion const&) / LLSelectMgr::saveSelectedObjectTransform - bushing Spatula
    • IMPORTED
  • VWR-2086 - Votes: 10 - Alt key no longer shows "physical" when pressed. - Cliff Commons
    • ALREADY IMPORTED
  • VWR-2004 - Votes: 1 - Map Search text box no highlight on first use - Savannah Nihilist
    • IMPORTED
  • VWR-2590 - Votes: 0 - Lose ability to view object contents after modifying cache - Emileigh Starbrook
    • IMPORTED
  • VWR-2266 - Votes: 2 - Friends list in Communicate window still shows (waiting) after 20 mins online - elmo dynamo
    • DUPLICATE
  • VWR-2550 - Votes: 2 - Scuplty vertex coordinates are size/256 meters too small on the positive faces - Acru Joliat
    • IMPORTED
  • VWR-2421 - Votes: 0 - ATI Radeon HD 2900 XT + Second Life = "Couldn't match GPU to a class","Setting GPU Class to Class0" - khamien mills
    • IMPORTED
  • VWR-2474 - Votes: 0 - Viewer crashes after reading 4 - 5 offline received notices - Big Enigma
    • DUPLICATE
  • VWR-2559 - Votes: 1 - inventory multi-preview windows can be scaled too small - Dildo Spitz
    • CANNOT REPRODUCE
  • VWR-2549 - Votes: 0 - odd case - public chat nonfunctional. im chat works fine. winxp, latest viewer, clean reinstall (new ui), disabled firewall. - anfrey tripsa
    • IMPORTED
  • VWR-2548 - Votes: 0 - Viewer locks up for 2 to 3 minutes when another avatar comes into view based on a camera movement resulting in disconnect - Strife Onizuka
    • IMPORTED
  • VWR-2532 - Votes: 0 - Buggy Texture Uplad - Anylyn Hax
    • CANNOT REPRODUCE
  • VWR-2347 - Votes: 0 - Viewer crash at last stage of log on (can hear IM notification beeps before crash) - Fluf Fredriksson
    • IMPORTED

Not new in 1.18.3.5 or RC 1.18.3, NOT 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/2007-10-10/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.