Bug triage/2008-12-03

Next meeting: 2008-12-03 at 3pm PST at Bridie Linden's house.

Import? 1.21 and 1.22 RC

• VWR-9650 - 9 votes - Severe client-side FPS drop during texture/prim rezzing - imnotgoing sideways
  • Try 1.22.2
• VWR-9792 - 6 votes - Audio stream keeps playing after quitting viewer. - gudrun gausman
  • Added Triaged Date
• VWR-10592 - 5 votes - All sounds in viewer cease when you close the first of --multiple SL sessions. - Damian Delacroix
  • Having tested internally
• VWR-10699 - 2 votes - Group Notices scroll up and down but sideways text is lost - Garn Conover
  • Resolved - Duplicate of VWR-8451

Import? 1.22 RC

• VWR-10587 - 4 votes - Aspect ratio settings broken under Linux fullscreen - Fox Hwasung
  • Imported
• VWR-10358 - 3 votes - Crash during login - Nvidia graphics card - Ellla McMahon
  • Added Triaged Dated
• VWR-10679 - 3 votes - unrezed textures for objects, avatars and particles all are a bright white - aaron23 decuir
  • Fixed
• VWR-10586 - 2 votes - RC 1.22 Dosent keep fullscreen mode - Fox Hwasung
  • Imported
• VWR-10645 - 2 votes - Saving a notecard positions the cursor at line 1 char 1 - Zuleika Deere
  • Imported
• VWR-10611 - 2 votes - UI turns dark or transparent when minimizing - Fox Hwasung
  • Added Triaged Date
• VWR-10672 - 1 votes - Muting does not "gray out" avatar after changing avatar impostors preference - feline slade
  • Imported
• VWR-10599 - 1 votes - Attached prims can only be selected sporadically from multiple angles for editing/interaction. - Millie Thompson
  • Needs More Information
• VWR-10777 - 1 votes - Inventory window turning transparent when dragging objects - Adger Ragu
  • Imported
• VWR-10789 - 1 votes - Minimap indicates an avatar, that is not visible. - James Benedek
  • Moved to Service

Import? 1.22 PN

• VWR-10546 - 2 votes - crash on loging after crash instead of "region has begun the logout process..." message - Cummere Mayo

Transcript

Transcript is/will be at Bug triage/2008/12/03/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)

• Look at the results of one of these queries
  • General triage: "Viewer 2 Bug Triage" (sorted by LL ID, Created, Last Triaged):
    • https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=12724
  • UI triage:
    • https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=10470 (The selected filter with id '10470' does not exist.)

  (Note: there's no hard and fast rule that says these are the only valid queries. If you feel there's a better query one particular week, use that.)

• Save a copy of the XML version of the query
• Run this perl script on the xml file

<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.

• if you do not have access to a perl interpreter. There is a ported version of the script on PHP, located here: http://jirafiller.technokittydevelopment.com/ made by roberto salubrius