Bug triage/2009-04-13

From Second Life Wiki
< Bug triage
Revision as of 10:15, 13 April 2009 by Harleen Gretzky (talk | contribs) (Added imported info to SVC-4100 and SVC-4107)
Jump to navigation Jump to search



Next meeting: 2009-04-13 at 12:00 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)

  • - SVC-4100 - Votes: 69 - 1.26.1 Server: Owner and Next Owner permissions are reversed when rezzing objects via scripts, linking the object to the rezzor and breaking the link - Lalwende Leakey - Last Triaged: 13/Apr/09 09:48 AM
    • Appears fixed with the reversion put into 1.26.2.117167 --Harleen Gretzky 04:23, 13 April 2009 (UTC)
    • got imported this morning as Linden Lab Issue ID: DEV-30577 needs to be resolved fix pending --Harleen Gretzky 17:15, 13 April 2009 (UTC)
  • - SVC-4107 - Votes: 67 - Changing object permissions in inventory sets owner permissions to new owner permissions - Ordinal Malaprop - Last Triaged: 13/Apr/09 09:41 AM
    • got imported as Linden Lab Issue ID: DEV-30575 this morning so maybe just need to resolve SVC-4093/SVC-4101 as duplicates of this issue --Harleen Gretzky 17:15, 13 April 2009 (UTC)
  • - SVC-4093 - Votes: 19 - since sever update to 1.26. i have to set all perms for next owner to full in my inventory b4 i rez them to edit - bikey bekkers
  • - SVC-4101 - Votes: 2 - Any self created items with no modify permissions set are not modifyable by the creator. - Sky Miles

Patches

Patches

Hot by Vote

Monday PJIRA Triage Filter (votes over 10, imported removed)

  • - SVC-1519 - Votes: 13 - Forwarding email to in-world object bounces - Dedric Mauriac - Last Triaged: 4/6/2009 12:00 PM
  • - SVC-3075 - Votes: 11 - Objects allowed to enter "No Object Entry" land against SIM borders. - mhisani naumova
  • - VWR-2726 - Votes: 11 - all inventory folders open - vida nemeth
  • - VWR-9974 - Votes: 11 - Snapshot: High-res snapshot results in 3 striped images or 9 tiled images - Hitomi Mokusei - Last Triaged: 11/5/2008 11:34 AM
  • - MISC-1520 - Votes: 10 - Items Rezzed In World Disappearing - Czari Zenovka
  • - SVC-2689 - Votes: 10 - While on beta grid on server 1.23 noticed that either one of two functions are destroyed. - Darkstar Heliosense
  • - SVC-3716 - Votes: 10 - llEmail() to an external email addres fails since jan/18 2009 - mandy medusa
  • - SVC-954 - Votes: 10 - Deleted user's Objects cannot be removed in bulk using the Estate Manager window. - Miscellaneous Fluffy
  • - VWR-1411 - Votes: 10 - Mac Voice Viewer doesn't allow you to specify OSX Core Audio devices channels - Emma Nowhere - Last Triaged: 12/9/2008 1:39 PM
  • - VWR-3849 - Votes: 10 - 12.15.07: Group owner can not view all members in group details - fredek petrov
  • - VWR-3879 - Votes: 10 - Underground Prims Visible through Linden Grass - Beezle Warburton
  • - VWR-4098 - Votes: 10 - Avatar hands frequently and seemingly randomly go open with spread fingers. - Vaelissa Cortes
  • - WEB-947 - Votes: 10 - Some last names are not completely retired - Adz Childs

Misc Pool

Monday PJIRA Triage Filter (votes under 10, imported removed)

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

  • - VWR-755 - Votes: 20 - Floating (Hover) Text penetrates walls - Ee Maculate
    • Waiting for more votes to import

Transcript

Transcript is/will be at Bug triage/2009-04-13/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.