Difference between revisions of "Bug Triage/Internationalization Agenda"

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


=== Resolved ===
=== Resolved ===
{{Bug List Instructions}}

Revision as of 13:17, 25 July 2007


Next meeting: 2007-07-27, 10am PDT at Iridium Linden's Haven in Beaumont. See Bug triage for details.

Bugfix Patches

Feature Request Patches

Other Bug Reports

  • VWR-1563 - Votes: 4 - Profile Mute button should display muted state (confuses international Residents) - Winter Ventura
  • VWR-721 - Votes: 4 - Dates are not displayed in the local date format - Jon Meriman
  • VWR-593 - Votes: 2 - Better display of UTF characters - catherine pfeffer
  • VWR-87 - Votes: 1 - Inappropriate texts in About floater translations - Alissa Sabre
  • VWR-112 - Votes: 1 - Arabic language needs to be displayed right to left rather than left to right - Rob Linden
  • VWR-298 - Votes: 1 - Practically impossible to enter Japanese text when viewer is running full-screen on MacOS - Alissa Sabre
  • VWR-1676 - Votes: 0 - Cmd+A causes the viewer to quit with french keyboards (Mac OS) - Ben Vanguard
  • VWR-335 - Votes: 0 - Needs two Chinese on Language selection - Alissa Sabre
  • VWR-1742 - Votes: 0 - Unicode problem when using Turkish alphabet characters in viewer. - Vixen Heron
  • VWR-1629 - Votes: 0 - Hebrew is not usable in the Viewer since 1.11/1.12 unless you have once installed at least 1.10 . - Smiley Barry
  • VWR-1593 - Votes: 0 - Improve localisation ability of Second Life - Gudmund Shepherd
  • VWR-1843 - Votes: 0 - Inappropriate default folder name for Make Outfit - Alissa Sabre
  • VWR-1889 - Votes: 0 - Search in classifieds for queries with German Umlauts is not case insensitive but yields different results depending on the case of the Umlaut - Peter Stindberg

Feature Request

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

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.