Bug triage/2008-12-29

From Second Life Wiki
< Bug triage
Revision as of 21:48, 27 December 2008 by Gordon Wendt (talk | contribs) (→‎Misc Pool: rm 7, reordering by number of votes)
Jump to navigation Jump to search



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

  • WEB-917 - Votes: 12 - Http 403 FORBIDDEN response when posting to forums - Jesse Barnett
  • SVC-2959 - Votes: 12 - HTerraforming "revert" option bypasses region terraforming limits - WarKirby Magojiro
    • Imported but a serious issue with a solid repro that appears to be a case of import and forget. GW (T|C) -- 05:17, 28 December 2008 (UTC)

Hot by Vote

High Voted Bugs

Patches

Patches

  • VWR-9540 - Votes: 2 - Statistics Bar position and on/off status not persistent between sessions - Dytska Vieria
  • VWR-11172 - Votes: 0 - A source coding mistake prevents number-pad keys from specifying Ctrl+digit shortcuts on Windows - Alissa Sabre

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

  • WEB-917 - Votes: 12 - Http 403 FORBIDDEN response when posting to forums - Jesse Barnett
    • Solid repro and fairly serious issue. GW (T|C) -- 00:28, 25 December 2008 (UTC)
  • SVC-2959 - Votes: 12 - HTerraforming "revert" option bypasses region terraforming limits - WarKirby Magojiro
    • Imported but a serious issue with a solid repro that appears to be a case of import and forget. GW (T|C) -- 05:18, 28 December 2008 (UTC)

Resolved

  • SVC-2797 - Votes: 11 - WindLight: llTargetOmega not working in linked objects - Sunn Thunders
    • Previously triaged and dealt with at 12-22 meeting, no updates since. GW (T|C) -- 05:28, 28 December 2008 (UTC)
  • VWR-7204 - Votes: 12 - Loading time of sculpts - Naiman Broome
    • Previously triaged and dealt with at 12-22 meeting, no updates since. GW (T|C) -- 05:28, 28 December 2008 (UTC)
  • SVC-3543 - Votes: 27 - Estate Tools & llTeleportAgentHome - Users with invalid homepoints are not removed from the sim, even when estate banned. - Drew Dwi
    • Previously triaged and dealt with at 12-22 meeting, no updates since. GW (T|C) -- 05:28, 28 December 2008 (UTC)
  • SVC-3556 - Votes: 12 - Intra-Region teleport not possible when region is full - Chalice Yao
    • Previously triaged and dealt with at 12-22 meeting, no updates since. GW (T|C) -- 05:28, 28 December 2008 (UTC)
  • VWR-11138 - Votes: 0 - Make develop.py play nicely with express editions of Visual Studio - Robin Cornelius
    • Previously triaged and dealt with. No updates or changes since. GW (T|C) -- 05:31, 28 December 2008 (UTC)
  • VWR-10311 - Votes: 2 - Enable LipSync by default - Mm Alder
    • Feature request, not a bug. GW (T|C) -- 05:31, 28 December 2008 (UTC)

Transcript

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