Difference between revisions of "Bug triage/2008-11-10"

From Second Life Wiki
Jump to navigation Jump to search
(→‎Imported: adding vwr-8932 to the log)
(→‎Misc Pool: adding VWR-5939)
Line 26: Line 26:


== Misc Pool ==
== Misc Pool ==
* {{jira|VWR-5939}} - Votes: 0 - All sound stops after leaving viewer open for a while. - {{User|Jessyka Richard}}
----
[http://www.sljirastats.com/jira_search.php?search=35&output=wiki Misc Pool]
[http://www.sljirastats.com/jira_search.php?search=35&output=wiki Misc Pool]



Revision as of 12:34, 11 November 2008


Next meeting: 2008-11-10 at 12:00PM 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-841 - Votes: 13 - Refer-A-Friend link no longer exchanges calling cards with new signups. No referral bonuses for accounts created after July 2008. - Adz Childs
  • WEB-510 - Votes: 11 - SLURL Map Contents Change According to the Map Zoom factor and/or Not Current - leo Linden
  • VWR-8759 - Votes: 12 - llTextBox in client shows blue !!TexTBox!! dialog - Kephra Nurmi
  • VWR-5287 - Votes: 12 - Prims turning Phantom on their own - stacyanne homewood
  • VWR-9172 - Votes: 11 - Frequent crashes as the result of right clicking - Zack Lockjaw
  • SVC-2464 - Votes: 11 - High User count produces Sim Time (other) constantly running at over 10ms+ - Drew Dwi
  • VWR-1111 - Votes: 32 - Scuplted Prims: Ability to Import .3DS Files - Dzonatas Sol
  • SVC-3259 - Votes: 14 - Logged out on failed teleport using Viewer 1.21 - magnet homewood

Patches

Patches

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

  • VWR-8932 - Votes: 20 - 1.21 RC - Script editor performance degrades with large scripts - WarKirby Magojiro
    • Imported to fast track section as it's a reoccuring bug with a solid repro. GW (T|C) -- 20:25, 11 November 2008 (UTC)

Resolved

  • SVC-3273 - Votes: 0 - llGetAgentLanguage is a violation of privacy, remove it - Yukinoroh Kamachi
    • Removed as this is not a technical issue but a policy one GW (T|C) -- 20:18, 11 November 2008 (UTC)
  • VWR-9801 - Votes: 0 - compilation of Puppeteering080323 client fails - tx Oh
    • Removed as it is my understanding that this branch has been discontinued GW (T|C) -- 20:23, 11 November 2008 (UTC)

Transcript

Transcript is/will be at Bug triage/2008-11-10/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.