Bug triage/2008-04-16

From Second Life Wiki
Jump to navigation Jump to search


Next meeting: 2008-04-16 at 3pm PST at Bridie Linden's house.

Import?

(Bugs reported in 1.20 RC0/RC1 — consider for import?, sorted by votes)

  • VWR-6350 - Votes: 12 - Word "Flycam" Appears In Flycam Mode, Does Not Disappear With UI - gonta maltz
    • Imported - Assigned to Rx
  • VWR-6399 - Votes: 11 - llMapDestination should still show teleport map -- Teleport / Map screen changes in 1.20 need to be undone - cobalt neutra
    • Imported - Assigned to Rx
  • VWR-5948 - Votes: 9 - Invisible Avatars, Transparent Clothes, Blanking Skies effected by various settings, Radeon HD Series - Kettu Keiko
    • Imported - Assigned to Pastramie Linden
  • VWR-6278 - Votes: 9 - DEV-3677 removes desired functionality (single click to sit by seated avatar) - Qie Niangao
    • Imported - Assigned to Triage
  • VWR-6262 - Votes: 8 - Text in windows (inventory, snapshot, preferences) and menus is not readable as there is too little contrast between the transparrent grey background and the blueish text in the Dazzle viewer. - Micah Giha
  • VWR-6274 - Votes: 7 - All textures momentarily flicker off - Feynt Mistral
    • Already Imported
  • VWR-5396 - Votes: 6 - Render Glow are appearing to be full glow on 1.19.1, 1.20 - Vincent Nacon
    • Duplicate
  • VWR-6425 - Votes: 6 - Windlight Default Settings Make Objects And Avatars Look Extremely Ugly - Brendan Cale
    • Duplicate - linked to VWR-6543
  • VWR-6402 - Votes: 4 - llTargetOmega resets prim to ZERO_ROTATION - Hampton Hax
    • Being Fixed
  • VWR-6400 - Votes: 3 - Invisible Avatar - Linzi Bingyi
    • Imported - Assigned to Pastrami Linden
  • VWR-6368 - Votes: 3 - Camera reset when build floater closes - Kirstyn Meredith
    • Imported - Assigned to Steve Linden
  • VWR-6269 - Votes: 3 - When Minimizing the Communicate Window, Text in Chat Console does not shows. - roberto salubrius
    • Already Imported
  • VWR-6358 - Votes: 3 - Joystick Support: OK and cancel buttons missing from the Joystick Configuration window. - Aimee Trescothick
    • Imported - Assigned to Rx
  • VWR-6439 - Votes: 3 - Script error dialog un-readable - BlueWall Slade
    • Duplicate of VWR-6488

Fast Track Import

(Move bugs here that have solid repros, or valid patches that you have reviewed)

Hot by Vote

High Voted Bugs

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

Resolved

  • VWR-6337 - Votes: 10 - Outline, Floating Text, Avatar Names, odd movement. - Lillium Elcar
    • Dupe of VWR-6244
  • VWR-6514 - Votes: 9 - 1.20 Preferences will not save - Krazzora Zaftig
    • Dupe of VWR-6298, Fix pending!
  • VWR-6455 - Votes: 4 - RC 1.20: -settings no longer works - Lazure Ryba
    • Dupe of VWR-6298, Fix pending!
  • VWR-6435 - Votes: 7 - Continuous crashing in new release candidate 1.20 - Naiman Broome
    • Dupe of VWR-6343 (imported and being investigated!)

Transcript

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