Bug triage/2007-12-12

From Second Life Wiki
Jump to navigation Jump to search


Next meeting:

Import?

(Bugs reported in 1.18.6.0 Release Candidate — consider for import?, sorted by votes)

  • VWR-3624 - Votes: 5 - SHIFT-X Align to Grid does misalign by 0.004m on X and Y axis and does NOT align on Z axis at all. - Squirrel Wood
  • VWR-3685 - Votes: 3 - Option to take off underwear and undershirt layer is missing from the pull down and pie menu's on the mac viewer - mouse mimistrobell
  • VWR-3667 - Votes: 1 - About Land > Access: On group owned land, group owner gets eject message when "Public Access" is unchecked. - Ceera Murakami
  • VWR-3789 - Votes: 1 - It is still possible for an non-age verified account to view, interact with, purchase content in a restricted parcel - Matthew Dowd
  • VWR-3672 - Votes: 1 - Mouse position for Log-in screen is incorrect on 2560 x 1600 display making log-in difficult - Rock Hayek
  • VWR-3687 - Votes: 1 - Preference settings not remembered; need to re-set all upon re-log - Milla Michinaga
  • VWR-3805 - Votes: 0 - Unable to attach clothing items after SL blog states issue resolved - Danger Lytton
  • VWR-3694 - Votes: 0 - IMs received whilst off line are displayed jumbled, and not in chronological order - Milla Michinaga
  • VWR-3702 - Votes: 0 - Marking text hand browser - Balp Allen
  • VWR-3799 - Votes: 0 - 1.18.6 Logon screen takes too long to finish loading. - Fluf Fredriksson
  • VWR-3737 - Votes: 0 - gstreamer fails to show videos on linux standalone builds - Michelle2 Zenovka
  • VWR-3787 - Votes: 0 - Meta-Issue: Age Verification Control Design Flaws - Matthew Dowd
  • VWR-3786 - Votes: 0 - Age verification can't protect content that is more than 50 M above terrain - Ceera Murakami
  • VWR-3782 - Votes: 0 - Search results not preserved on open/close - Lee Ludd
  • VWR-3731 - Votes: 0 - Camera and movement controls are displayed on the login screen of slviewer v1.18.6.0RC - Henri Beauchamp
  • VWR-3730 - Votes: 0 - memory leak - aaron23 decuir
  • VWR-3682 - Votes: 0 - Ban and access limits no longer showing - Jini Hammerer
  • VWR-3766 - Votes: 0 - llGetInventoryNumber tooltip missing INVENTORY_ANIMATION - Dedric Mauriac
  • VWR-3794 - Votes: 0 - newview/files.lst: separate out llappviewer*.cpp dependencies into files.platform.lst - Dzonatas Sol

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

  • VWR-3669 - Votes: 2 - Version information at login screen is URL Encoded - march Korda
    • Linked to internal issue: DEV-6625

Resolved

  • VWR-3802 - Votes: 0 - Viewer version info padded with %20's making it hard to decipher - Azadine Umarov
    • Dupe of VWR-3669

Transcript

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