Bug triage/2007-11-26

From Second Life Wiki
< Bug triage
Revision as of 10:16, 18 December 2007 by Bridie Linden (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Next meeting: 2007-11-26 at 12pm SLT in Hippotropolis. See Bug triage for details.

Fast Track Import

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

Hot

  • WEB-382 - Votes: 2 - Bugs and Proposals on the JIRA Cannot Be Closed or Moved Without Author Consent - Prokofy Neva
  • WEB-380 - Votes: 19 - ""Fixed Internally"" should not appear as ""Resolved"" in JIRA; voting should continue - Ordinal Malaprop

Patches

  • VWR-1917 - Votes: 9 - Have Friends and Groups display in a seperate window when accessed via menus. Add short cut for Groups - Matthew Dowd
  • VWR-3060 - Votes: 3 - Add a setting to hide the IMs in the main chat. - Henri Beauchamp
  • VWR-3087 - Votes: 4 - Allow for hiding the ""Release Keys"" button and ""Master Remote"" volume control. - Henri Beauchamp
  • VWR-3093 - Votes: 3 - Allow MU* (MUCK, MUSH, MUX, MUD) like ""poses"" (=IRC emotes) in chat and IMs. - Henri Beauchamp
  • VWR-3202 - Votes: 0 - Make chat console background color customizable - Jacek Antonelli
  • VWR-3206 - Votes: 0 - OpenJPEG svn478 causes slviewer to crash - Seg Baphomet
  • VWR-3290 - Votes: 0 - Linux scons build script doesn't work with distcc - Alissa Sabre
  • VWR-3292 - Votes: 0 - llsphere.cpp lat2xyz inefficiencies - Haravikk Mistral
  • VWR-3340 - Votes: 0 - Login State change should display the definition and not the code itself - Whoops Babii
  • VWR-3410 - Votes: 0 - Alissa's on-the-spot (aka inline) IME patch generates too many typing sounds when chatting in Japanese - Alissa Sabre
  • VWR-3419 - Votes: 1 - Reduce compiled object file at 10% by omitting unused information such as function name(it's emptry string) and optimizing generated assembly code sequence. - Chiyosuke Wise
  • VWR-3458 - Votes: 0 - Mouse cursor background is opaque white instead of transparent on big endian systems - MrCooper Merlin

Misc Pool

  • VWR-1793 - Votes: 11 - Hand Poses Not Uploaded Correctly - cracker hax
  • VWR-3133 - Votes: 12 - Meta-Issue: WindLight: Bringing shiny on par with non-WindLight viewer (and beyond) - Elle Pollack
  • VWR-3171 - Votes: 12 - Local Lighting Exposure in Windlight seems to be greatly lessened. - Aradia Dielli
  • VWR-3258 - Votes: 14 - VBO render bug with objects on ATI graphics cards blocking the view. - Trice Beam
  • WEB-175 - Votes: 11 - Credit card not going through (failure then not authorized) - Rylei Korhonen
  • WEB-380 - Votes: 19 - ""Fixed Internally"" should not appear as ""Resolved"" in JIRA; voting should continue - Ordinal Malaprop

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/2007-11-26/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.