Difference between revisions of "Bug triage/2009-12-07"

From Second Life Wiki
Jump to navigation Jump to search
Line 20: Line 20:


* {{jira|SVC-5097}} - Votes: 72 - Simulator Time statistics inaccurate, AKA Mystery Lag that is Primarily caused by object positional updates. - {{User|NeoBokrug Elytis}}
* {{jira|SVC-5097}} - Votes: 72 - Simulator Time statistics inaccurate, AKA Mystery Lag that is Primarily caused by object positional updates. - {{User|NeoBokrug Elytis}}
** Resolved - Needs more info


== Misc Pool ==
== Misc Pool ==

Revision as of 09:51, 8 December 2009



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

  • VWR-2090 - Votes: 2 - When IMs from objects are capped, the first IM sent is lost. This also needs to be changed from a viewer issue to a server issue. - Sayrah Parx
    • Imported

Hot by Vote

High Voted Bugs

  • SVC-5097 - Votes: 72 - Simulator Time statistics inaccurate, AKA Mystery Lag that is Primarily caused by object positional updates. - NeoBokrug Elytis
    • Resolved - Needs more info

Misc Pool

Misc Pool

  • SVC-5101 - Votes: 0 - Uncontrolable hand movement and being in different postions, without myself seeing it - DD Otoole
  • SVC-4365 - Votes: 1 - "Avatars who deselect "Show In Search" are now completely hidden and cannot be contacted by IM or notecard/object drop. Their profiles are completely inaccessible." - Lodi McMillan
  • SVC-2441 - Votes: 9 - Slowish llMoveToTarget path inconsistent when moving to a target at a -z position vs moving to +z - Sindy Tsure
  • SVC-522 - Votes: 9 - Default script should NOT use llSay() for Hello Avatar; use llOwnerSay() instead. - Neo Rebus


  • VWR-7585 - Votes: 9 - "Changing antialiasing settings results in everything rendering as black (except floating windows, HUD attachments and glows)" - Warin Cascabel
  • WEB-1381 - Votes: 9 - "Click on post link in member profile does not take you to post, but to end of thread" - Lane Luke

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

Transcript

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