Difference between revisions of "Bug triage/2007-11-07"
Jump to navigation
Jump to search
Line 10: | Line 10: | ||
==== Not new in 1.18.3.5 or RC 1.18.3, NOT Imported ==== | ==== Not new in 1.18.3.5 or RC 1.18.3, NOT Imported ==== | ||
* {{jira|VWR-2182}} - Votes: 0 - Vivox Daemon Crashes - {{User|otakup0pe neumann}} | * {{jira|VWR-2182}} - Votes: 0 - Vivox Daemon Crashes - {{User|otakup0pe neumann}} | ||
* {{jira|VWR-2437}} - Votes: 0 - Minor glitches using ATIs Beta 8.41 driver for Linux - {{User|Sariel Villota}} | * {{jira|VWR-2437}} - Votes: 0 - Minor glitches using ATIs Beta 8.41 driver for Linux - {{User|Sariel Villota}} |
Revision as of 09:18, 15 October 2007
Next meeting: 2007-10-08 at 3pm at Bridie's Place in Linden Village. See Bug triage for details.
Fast Track Import
(Move bugs here that have solid repros, or valid patches that you have reviewed)
New in 1.18.3.5 or RC 1.18.3?, NOT Imported
Not new in 1.18.3.5 or RC 1.18.3, NOT Imported
- VWR-2182 - Votes: 0 - Vivox Daemon Crashes - otakup0pe neumann
- VWR-2437 - Votes: 0 - Minor glitches using ATIs Beta 8.41 driver for Linux - Sariel Villota
- VWR-2496 - Votes: 2 - Linking 255 or 256 prims results in two linksets - Ochi Wolfe
- VWR-2490 - Votes: 0 - "BAD_OSS" in startup script makes login hang - Boroondas Gupte
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-07/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)
- Look at the results of one of these queries
- General triage: "Viewer 2 Bug Triage" (sorted by LL ID, Created, Last Triaged):
- UI triage:
- https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=10470 (The selected filter with id '10470' does not exist.)
- (Note: there's no hard and fast rule that says these are the only valid queries. If you feel there's a better query one particular week, use that.)
- Save a copy of the XML version of the query
- Run this perl script on the xml file
<perl>
- !/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.
- if you do not have access to a perl interpreter. There is a ported version of the script on PHP, located here: http://jirafiller.technokittydevelopment.com/ made by roberto salubrius