Bug triage/2009-05-21

Next meeting: 2009-05-21 at 2:30 AM SLT at Louise's Office in Cirano. See Bug triage for details.

1.23 RC/PN by vote

• VWR-13137 - 4 votes - invisible avatar - Arizona Davies
  • Resolved - Needs More Information
• VWR-13328 - 4 votes - All my bot models are smoke clouds - Katherine Comet
  • Resolved - Needs More Information
• VWR-13498 - 3 votes - RC Camera angle/FOV is much narrower - Stickman Ingmann
  • Imported
• VWR-13095 - 3 votes - Transparent Avatars when using Models on the JVA Software & other similar software. - Sapphire Oh
  • Resolved - Expected Behaviour
• VWR-13240 - 3 votes - Objects sent while in busy mode go to objects folder, not trash - Taryn London
  • May be expected behaviour - Imported
• VWR-13490 - 3 votes - Font readability in RC - Sharron Schuman
  • Resolved - Needs More Information
• VWR-13037 - 3 votes - Changing access rating preference resulted in incorrectly sending pg restricted to mature region then reset homepoint - Cummere Mayo
  • Imported
• VWR-13421 - 2 votes - Alpha sorting issues much worse in this release - Veggieson Ballyhoo
  • Imported
• VWR-13079 - 2 votes - Unknown Alert message - expired_region_handoff - Charlene Trudeau
  • Resolved - Fixed
• VWR-13226 - 2 votes - Objects don't load when the focus is on internal html windows (search all, etc) - Bofp Boyd
  • Imported
• VWR-13430 - 2 votes - Multiple Popups do not show arrow to go to next Popup - sera lok
  • Resolved - Fixed
• VWR-13076 - 2 votes - bottom of letters/writing missing/faded out - Mags Indigo
  • Resolved - Needs More Information
• VWR-12955 - 2 votes - Changing Antialiasing before login gives weird screen until apply is clicked - Lares Carter
  • Imported
• VWR-2702 - 1 votes - Leaving groups in Latest RC does not update in the client. - Tmyclyk Dmytryk
  • Resolved - Needs More Information
• VWR-13313 - 1 votes - No Glow on 1.23 Release Canidate (Mac OS X) (also XP) - Xanthos Exonar
  • Resolved - Needs More Information

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

• VWR-13316 - 11 votes - Cant copy an attached item to another folder of my inventory. Need this feature back, cause if somebody edit an attached item and do a mistake, you need to copy the attachment for rescue it back. - Larissa Vacano
• VWR-13038 - 9 votes - Underlapping of what should be overlapping prims in an object. Additionally failer to set shiney after scripted alpha was released. - EddyFragment Robonaught
• VWR-3780 - 9 votes - Rotated textures stretch incorrectly when stretching prims with "Stretch Textures" un-checked - Cocoanut Koala
• VWR-13349 - 5 votes - Grid is marred by a sub grid which does not disable and makes grid visually unusable, when using it on a plane. - Kaine Lowenstark
• VWR-12933 - 5 votes - After Login Textures take a long time to Load. - MAtto Destiny

Resolved

• VWR-13294 - 4 votes - Disappearing prims - Cinnamon Ahn

Duplicate of internal DEV-32013

Triaged in Wednesday triage

• VWR-13594 - 40 votes - While entering SIM, or walking close to a SIM i get unbelievable high SIM ping and FPS dropping down nearly zero - Karoline Merlin

NMI

Transcript

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