Bug triage/2009-03-09

From Second Life Wiki
Jump to: navigation, search



Next meeting: 2009-03-09 at 12:00 PM SLT at Hippotropolis Meeting areaD. 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-982 - Votes: 15 - Problems for blogs.secondlife.com - Argent Stonecutter
  • SVC-1817 - Votes: 11 - Residents with proper SPF records cannot submit abuse reports because the sims spoof their email address and indra-abuse@secondlife.com honors SPF for all senders - BamBam Sachertorte

Patches

Patches

no patches this week, for editing notes on haikus see talk page - G.W.

Misc Pool

Misc Pool

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: 18 - Floating (Hover) Text penetrates walls - Ee Maculate
    • Previously Linden marked as will not finish but kept open for votes. GW (T|C) -- 05:48, 9 March 2009 (UTC)
  • VWR-11930 - Votes: 0 - Teleporting either Disconnects or Crashes SL - Flurry Parx
    • Resolved on JIRA, dupe. GW (T|C) -- 06:03, 9 March 2009 (UTC)
  • SVC-3182 - Votes: 0 - Payment received by one vendor ended up in another avatar's transaction history - Timeless Prototype
    • Disappeared into SEC-190 so can't triage. GW (T|C) -- 06:03, 9 March 2009 (UTC)
  • VWR-8374 - Votes: 0 - bandwidth indicator does not fit - wulfric chevalier
    • Resolved on JIRA, NMI. GW (T|C) -- 06:03, 9 March 2009 (UTC)
  • SVC-3890 - Votes: 0 - texturechange scripts refuse to work in class4 sims - Yuukie Onmura
    • In dispute on JIRA but comment consensus is NMI before it can be dealt with. GW (T|C) -- 06:03, 9 March 2009 (UTC)
  • VWR-3063 - Votes: 0 - Crash during tp - Luxarnia Dagger
    • Resolved on JIRA, NMI. GW (T|C) -- 06:03, 9 March 2009 (UTC)
  • VWR-3032 - Votes: 0 - Linked parts, when copied will unlink the original copied from - Marc Montague
    • Resolved on JIRA, NMI. GW (T|C) -- 06:09, 9 March 2009 (UTC)
  • VWR-2978 - Votes: 0 - llRequestAgentData does not respect Make my online status visible only to friends setting - Earl Pinion
    • Still open because reference couldn't be found but Lindens have stated in the past that they won't change this. GW (T|C) -- 06:09, 9 March 2009 (UTC)
  • VWR-5329 - Votes: 0 - click and crash - shadow pawpaw
    • Resolved, NMI. GW (T|C) -- 06:14, 9 March 2009 (UTC)

Transcript

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