Bug triage/2007-11-19
From Second Life Wiki
QA Portal > Bug triage > Bug triage/2007-11-19
Next meeting: 2007-11-19 at Monday, 12pm PST at the Hippotropolis Meeting area
Contents |
Features
- This one isn't a top voted feature (yet), but between the bug and associated feature, it's near the top. Gigs Taggart
- SVC-913[c] - Votes: 69 - Allow LSL scripts to act as HTTP servers in order to replace XMLRPC with something scalable - Sean Linden
- Imported - Assigned to Sean Linden
- SVC-29[c] - Votes: 94 - XMLRPC sporadically (but usually) very slow - Apotheus Silverman
- If a resident will send an email to the SL Dev team, Rob Linden will follow up.
- WEB-382[c] - Votes: 2 - Bugs and Proposals on the JIRA Cannot Be Closed or Moved Without Author Consent - Prokofy Neva
- Closed - Needs more info
- VWR-3071[c] - Votes: 1 - Objects Set for Sale should not default to "Show in Search" - Prokofy Neva
- Imported - Assigned to Rob Linden
- In review as of this posting
Fast Track Import
(Move bugs here that have solid repros, or valid patches that you have reviewed)
- WEB-383[c] - Votes: 0 - membership plans page is out of date - Gigs Taggart
- Imported - Assigned to Jeff Linden
Hot by Vote
- WEB-380[c] - Votes: 11 - "Fixed Internally" should not appear as "Resolved" in JIRA; voting should continue - Ordinal Malaprop
- Imported - Assigned to Rob Linden
- MISC-488[c] - Votes: 12 - rez objects only works if i'm online - october brotherhood
- Changed to SVC
- Imported - Assigned to Aric Linden
Patches
- VWR-3272[c] - Votes: 3 - Shader support removed in Windlight for some cards that work well (when it is re-enabled) - Abyssin Otoro
- Imported - Assigned to Windlight Team
- VWR-3265[c] - Votes: 0 - IM Tabs stack vertical rather than horizontal (Yet another solution to the communicate window) - Matthew Dowd
- Imported - Assigned to RX Team
- VWR-1549[c] - Votes: 7 - Move Friends and Groups tabs from left to bottom - Matthew Dowd
- Imported - Assigned to RX Team
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
- A little vague, and original reporter and others have reported lower levels of crashing now Gigs Taggart
Transcript
Transcript is/will be at Bug Triage/2007-11-19/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:
- Copy the markup from Template:Triage Template as a starting point for your agenda. One wiki trick you can employ is to save "{{subst:Triage Template}}" as the complete markup of a new page. Doing this is the equivalent of copying and pasting the full markup of the template in.
- Look at the results of one of these queries
- General triage: "Bugs, sorted by LL ID"):
- UI triage:
- (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
#!/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 "* {{jira|$key}} - Votes: $votes - $title - {{User|$reporter}}\n"; }
- Pick a reasonable cutoff point, and copy the output into the appropriate section of your newly created page.

