Difference between revisions of "Bug triage/2007-12-17"

From Second Life Wiki
Jump to navigation Jump to search
Line 15: Line 15:
== Patches ==
== Patches ==
* {{jira|VWR-3655}} - Votes: 0 - Extra qualifier in LLWaterParamSet definition, making gcc choke (considered an error). - {{User|Henri Beauchamp}}
* {{jira|VWR-3655}} - Votes: 0 - Extra qualifier in LLWaterParamSet definition, making gcc choke (considered an error). - {{User|Henri Beauchamp}}
** Imported - Assigned to Soft Linden
* {{jira|VWR-3813}} - Votes: 1 - gtk_check_version() API changed to return const gchar * - causes gcc ERROR - {{User|Michelle2 Zenovka}}
* {{jira|VWR-3813}} - Votes: 1 - gtk_check_version() API changed to return const gchar * - causes gcc ERROR - {{User|Michelle2 Zenovka}}
** Imported - Assigned to Soft Linden
* {{jira|VWR-3835}} - Votes: 1 - Copy UUID Pie Menu Item - {{User|Eddy Stryker}}
* {{jira|VWR-3835}} - Votes: 1 - Copy UUID Pie Menu Item - {{User|Eddy Stryker}}
** Imported - Assigned to RX


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

Revision as of 12:13, 18 December 2007


Next meeting: 2007-XX-XX at TIME and PLACE (FIXME). See Bug triage for details.

Fast Track Import

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

Hot by Vote

  • SVC-1032 - Votes: 11 - Age Verification status shows in profile - WarKirby Magojiro
    • Fixed
  • SVC-1072 - Votes: 39 - Havok 4 -- Objects can exist up to 4096 meters up, but scripted rez above 1024 meters fails silently - Jcool410 Wildcat
    • Linked to DEV-7422

Patches

  • VWR-3655 - Votes: 0 - Extra qualifier in LLWaterParamSet definition, making gcc choke (considered an error). - Henri Beauchamp
    • Imported - Assigned to Soft Linden
  • VWR-3813 - Votes: 1 - gtk_check_version() API changed to return const gchar * - causes gcc ERROR - Michelle2 Zenovka
    • Imported - Assigned to Soft Linden
  • VWR-3835 - Votes: 1 - Copy UUID Pie Menu Item - Eddy Stryker
    • Imported - Assigned to RX

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

Transcript

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