Bug triage/2008-06-23

Next meeting: 2008-06-23 at 12 PM 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)

Hot by Vote

High Voted Bugs

• WEB-510 - Votes: 11 - SLURL Map Contents Change According to the Map Zoom factor and/or Not Current - leo Linden
• VWR-7474 - Votes: 11 - Frequent hanging - Timothy Oconnell
• SVC-1060 - Votes: 13 - Some parcels are not indexed in new search - Rifkin Habsburg
• SVC-2433 - Votes: 11 - Zephyr Chimes v1.1 does not work correctly on Havok4 simulators. - beatfox xevious
• VWR-7843 - Votes: 30 - SL clients are receiving *far too many avatar textures unnecessarily* - Hypatia Callisto
• SVC-2426 - Votes: 20 - llPushObject in attachment pushing the person wearing it has stopped working with update 121 - darling brody
• SVC-2513 - Votes: 15 - Push (llPushObject) not working correctly when applied to an avatar! - Abramelin Wolfe

Patches

Patches

• VWR-7606 - Votes: 0 - REGION_FLAGS_BLOCK_PUPPETEERING collides with REGION_FLAGS_BLOCK_PARCEL_SEARCH - Strife Onizuka
• VWR-7708 - Votes: 2 - New constant PRIM_TEMPORARY - Strife Onizuka
• VWR-7362 - Votes: 1 - Add LSL constant EMPTY_KEY as (key)"""" please - meade paravane
• VWR-7877 - Votes: 2 - Change the default cut increment from 0.05 to 0.025 - McCabe Maxsted
• VWR-7802 - Votes: 0 - Save texture does not use texture name for default file name - JB Kraft

Misc Pool

Misc Pool

• VWR-6116 - Votes: 6 - Seeing only two local lights active (excluding sun and moon) - Bree Giffen
  • Someday - Maybe

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.

Transcript

Transcript is/will be at Bug triage/2008-06-23/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