Difference between revisions of "Bug triage/2007-11-19"

From Second Life Wiki
Jump to navigation Jump to search
Line 24: Line 24:
== Hot by Vote ==
== Hot by Vote ==


* {{jira|WEB-380}} - Votes: 11 - "Fixed Internally" should not appear as "Resolved" in JIRA; voting should continue - {{User|Ordinal Malaprop}}
* {{jira|MISC-488}} - Votes: 12 - rez objects only works if i'm online - {{User|october brotherhood}}


* {{jira|VWR-3004}} - Votes: 13 - random crashes on recent linux clients - {{User|tx Oh}}
* {{jira|MISC-488}} - Votes: 12 - rez objects only works if i'm online - {{User|october brotherhood}}
* {{jira|WEB-380}} - Votes: 11 - "Fixed Internally" should not appear as "Resolved" in JIRA; voting should continue - {{User|Ordinal Malaprop}}


== Patches ==
== Patches ==
Line 69: Line 68:


=== Resolved ===
=== Resolved ===
* {{jira|VWR-3004}} - Votes: 13 - random crashes on recent linux clients - {{User|tx Oh}}
:A little vague, and original reporter and others have reported lower levels of crashing now [[User:Gigs Taggart|Gigs Taggart]]


== Transcript ==
== Transcript ==

Revision as of 08:03, 19 November 2007


Next meeting: 2007-11-19 at Monday, 12pm PST at the Hippotropolis Meeting area

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 - Votes: 69 - Allow LSL scripts to act as HTTP servers in order to replace XMLRPC with something scalable - Sean Linden
  • SVC-29 - Votes: 94 - XMLRPC sporadically (but usually) very slow - Apotheus Silverman


  • WEB-382 - Votes: 2 - Bugs and Proposals on the JIRA Cannot Be Closed or Moved Without Author Consent - Prokofy Neva
  • VWR-3071 - Votes: 1 - Objects Set for Sale should not default to "Show in Search" - Prokofy Neva

Ping on VWR-442

Fast Track Import

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


Hot by Vote


Patches

  • VWR-3272 - Votes: 3 - Shader support removed in Windlight for some cards that work well (when it is re-enabled) - Abyssin Otoro
  • VWR-3265 - Votes: 0 - IM Tabs stack vertical rather than horizontal (Yet another solution to the communicate window) - Matthew Dowd
  • VWR-3206 - Votes: 0 - OpenJPEG svn478 causes slviewer to crash - Seg Baphomet
  • VWR-3202 - Votes: 0 - Make chat console background color customizable - Jacek Antonelli
  • VWR-3093 - Votes: 1 - Allow MU* (MUCK, MUSH, MUX, MUD) like "poses" (=IRC emotes) in chat and IMs. - Henri Beauchamp
  • VWR-3087 - Votes: 2 - Allow for hiding the "Release Keys" button and "Master Remote" volume control. - Henri Beauchamp
  • VWR-3060 - Votes: 0 - Add a setting to hide the IMs in the main chat. - Henri Beauchamp
  • VWR-1917 - Votes: 8 - Have Friends and Groups display in a seperate window when accessed via menus. Add short cut for Groups - Matthew Dowd
  • VWR-1549 - Votes: 7 - Move Friends and Groups tabs from left to bottom - Matthew Dowd


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

  • VWR-3004 - Votes: 13 - random crashes on recent linux clients - tx Oh
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:


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.