Bug triage/2007-06-25

Misc Pool

• SVC-358 - Votes: 0 - Couldnt "Read" the memory when enable full screen! - fatepower snook
• VWR-1358 - Votes: 0 - Some transparent objects show up as if highlight transparent was enabled - Dale Glass
• VWR-1357 - Votes: 0 - SLVoice subapp sends voice data when Talk is not pressed, but push-to-talk IS enabled - Llewelyn Mistral
• SVC-356 - Votes: 0 - llCreateLink can fail to link sets of linked prims - Eata Kitty
• WEB-187 - Votes: 0 - spurious --> symbols in transaction history - Lex Neva
• VWR-1355 - Votes: 0 - Implementation of next_power_of_two in llmath/llvolume - Nicholaz Beresford
• VWR-1354 - Votes: 1 - Possible crash in lldrawpool - Nicholaz Beresford
• VWR-1353 - Votes: 1 - Misleading variable names in LLTextEditor - Alissa Sabre
• VWR-1352 - Votes: 1 - A strange copy operation of LLStyle - Alissa Sabre
• VWR-1351 - Votes: 1 - Violation against the conding standard in llfloaterchat.cpp - Alissa Sabre
• MISC-334 - Votes: 0 - Missing inventory after login - bettina wunderlich
• VWR-1350 - Votes: 0 - Color settings do not appear to be applied to LSL default text - kerutsen sellery
• WEB-186 - Votes: 0 - Billing and Trading Limits Error - Jericho Drake
• MISC-333 - Votes: 11 - Animated sculpties - nomasha syaka
• VWR-1347 - Votes: 0 - Head transparent in changing appearance - Benja Kepler
• VWR-1345 - Votes: 0 - Voice client lacks the ability to mute objects from chat history - atlwolf blabbermouth
• VWR-1343 - Votes: 0 - SL Crashes with nVIDIA Stereo driver - Kyra Arkin
• VWR-1342 - Votes: 0 - Can initiate/join group voice chat. Cannot initiate spatial or individual voice chat. - Ryu Darragh
• VWR-1341 - Votes: 0 - optional sound devices don't work in outer islands, also trouble connecting to voice - AmigaDragon Greatrex
• WEB-185 - Votes: 0 - HTML in support link - SignpostMarv Martin
• VWR-1340 - Votes: 0 - " Active Group" above name wil not display - Oddr Stenvaag
• SVC-352 - Votes: 0 - Login fails sporadically - Sadako Shikami

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