Difference between revisions of "Bug triage/2007-07-16"

From Second Life Wiki
Jump to navigation Jump to search
(resolved one)
Line 9: Line 9:


Probably Safe:
Probably Safe:
* {{jira|VWR-1704}} - indra/llui/files.lst: delete llhtmlhelp.h entry - [[User:Dzonatas_Sol|Dzonatas Sol]]
* {{jira|VWR-1705}} - indra/lscript/lscript_compile/indra.y: disable compiler warning #4065 for 'switch' statements - [[User:Dzonatas_Sol|Dzonatas Sol]]
* {{jira|VWR-779}} - Votes: 0 - Texture-Debug-View (Shift+Ctrl+3) with various layout quirks - {{User|Nicholaz Beresford}}
* {{jira|VWR-779}} - Votes: 0 - Texture-Debug-View (Shift+Ctrl+3) with various layout quirks - {{User|Nicholaz Beresford}}
* {{jira|VWR-940}} - Votes: 0 - llfasttimers.h/cpp: improved timer code and allowed support for linux platforms other than i386 - {{User|TBBle Kurosawa}}
* {{jira|VWR-940}} - Votes: 0 - llfasttimers.h/cpp: improved timer code and allowed support for linux platforms other than i386 - {{User|TBBle Kurosawa}}
Line 49: Line 47:


=== Imported ===
=== Imported ===
* {{jira|VWR-1704}} - indra/llui/files.lst: delete llhtmlhelp.h entry - [[User:Dzonatas_Sol|Dzonatas Sol]]
* {{jira|VWR-1705}} - indra/lscript/lscript_compile/indra.y: disable compiler warning #4065 for 'switch' statements - [[User:Dzonatas_Sol|Dzonatas Sol]]


=== Resolved ===
=== Resolved ===

Revision as of 06:50, 16 July 2007

Next meeting: 2007-07-16. See Bug triage for details.

Fast Track Import

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

Patches

Probably Safe:

  • VWR-779 - Votes: 0 - Texture-Debug-View (Shift+Ctrl+3) with various layout quirks - Nicholaz Beresford
  • VWR-940 - Votes: 0 - llfasttimers.h/cpp: improved timer code and allowed support for linux platforms other than i386 - TBBle Kurosawa

Potentially Controversial:

  • SVC-337 - Votes: 0 - MuteFlags set in a UpdateMuteListEntry message are discarded - able whitman

Hot by Vote


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

Can't reproduce, and I asked around and no one else was seeing it either. Gigs Taggart 03:40, 16 July 2007 (PDT)


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.