Difference between revisions of "Bug triage/2008-02-04"
Jump to navigation
Jump to search
(New page: {{Bug triage}} Next meeting: 2008-02-04 at 12pm PST and {{SLurl|region=Hippotropolis|x=241|y=27|z=23|title=Hippotropolis Meeting area}}. See Bug triage for details. == Fast Track Im...) |
(No difference)
|
Revision as of 07:36, 4 February 2008
Next meeting: 2008-02-04 at 12pm PST and Hippotropolis Meeting area🖈. See Bug triage for details.
Fast Track Import
- SVC-1394 - Votes: 4 - New server rollouts (1/31) break llSetObjectDesc() / llGetObjectDesc() - Doran Zemlja
- OP refuses to resolve until a Linden chimes in
- MISC-907 - Votes: 0 - Major Bork Bork Bork after the restarts today 31 jan 2008 in object name, description - Chaz Longstaff
- SVC-1415 - Votes: 8 - 2/1/08 rolling restart breaks llSensor() - Huns Valen
- MISC-912 - Votes: 11 - Checking item to "show in search" toggles back off when you close edit window - BUT: Works on islands running latest havok engine - Shanti Sands
- SVC-54 - Votes: 33 - llTargetOmega doesn't update unless object is interacted with by an AV - Heather Goodliffe
- Broke again on 1.19 servers
(Move bugs here that have solid repros, or valid patches that you have reviewed)
Hot by Vote
Patches
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/2008-02-04/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