Difference between revisions of "Bug triage/2009-03-30"

From Second Life Wiki
Jump to navigation Jump to search
(Added auto-lists)
(Moved SVC-3182 and VWR-8374 to resolved section)
Line 18: Line 18:
* {{jira|SVC-3969}} - Votes: 29 - Simulators Getting Listed in CBL DNSBL - {{User|Gigs Taggart}}
* {{jira|SVC-3969}} - Votes: 29 - Simulators Getting Listed in CBL DNSBL - {{User|Gigs Taggart}}
* {{jira|SVC-2489}} - Votes: 18 - Group - Abilities - Parcel Powers - Always Allow 'Create Object' is being ignored. - {{User|Cheta Torok}}
* {{jira|SVC-2489}} - Votes: 18 - Group - Abilities - Parcel Powers - Always Allow 'Create Object' is being ignored. - {{User|Cheta Torok}}
* {{jira|VWR-755}} - Votes: 18 - Floating (Hover) Text penetrates walls - {{User|Ee Maculate}}
* {{jira|SVC-391}} - Votes: 11 - llEmail and llHTTPRequest do not handle non-ASCII characters - {{User|Omei Turnbull}}
* {{jira|SVC-391}} - Votes: 11 - llEmail and llHTTPRequest do not handle non-ASCII characters - {{User|Omei Turnbull}}


Line 34: Line 33:
* {{jira|VWR-11930}} - Votes: 0 - Teleporting either Disconnects or Crashes SL - {{User|Flurry Parx}}
* {{jira|VWR-11930}} - Votes: 0 - Teleporting either Disconnects or Crashes SL - {{User|Flurry Parx}}
* {{jira|VWR-12070}} - Votes: 1 - Extreme lag with voice enabled. - {{User|Kitten Ree}}
* {{jira|VWR-12070}} - Votes: 1 - Extreme lag with voice enabled. - {{User|Kitten Ree}}
* {{jira|SVC-3182}} - Votes: 0 - Payment received by one vendor ended up in another avatar's transaction history - {{User|Timeless Prototype}}
* {{jira|VWR-8374}} - Votes: 0 - bandwidth indicator does not fit - {{User|wulfric chevalier}}
* {{jira|VWR-3063}} - Votes: 0 - Crash during tp - {{User|Luxarnia Dagger}}
* {{jira|VWR-3063}} - Votes: 0 - Crash during tp - {{User|Luxarnia Dagger}}
* {{jira|VWR-3032}} - Votes: 0 - Linked parts, when copied will unlink the original copied from - {{User|Marc Montague}}
* {{jira|VWR-3032}} - Votes: 0 - Linked parts, when copied will unlink the original copied from - {{User|Marc Montague}}
Line 60: Line 57:


=== Imported ===
=== Imported ===
 
* {{jira|VWR-755}} - Votes: 18 - Floating (Hover) Text penetrates walls - {{User|Ee Maculate}}
=== Resolved ===
=== Resolved ===
 
* {{jira|SVC-3182}} - Votes: 0 - Payment received by one vendor ended up in another avatar's transaction history - {{User|Timeless Prototype}}
* {{jira|VWR-8374}} - Votes: 0 - bandwidth indicator does not fit - {{User|wulfric chevalier}}
== Transcript ==
== Transcript ==
Transcript is/will be at [[Bug triage/{{#var:date}}/Transcript]]
Transcript is/will be at [[Bug triage/{{#var:date}}/Transcript]]

Revision as of 02:53, 30 March 2009



Next meeting: 2009-03-30 at 12:00 PM SLT at Hippotropolis Meeting area🖈. See Bug triage for details.

Fast Track Import

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

Hot by Vote

High Voted Bugs

  • SVC-3969 - Votes: 29 - Simulators Getting Listed in CBL DNSBL - Gigs Taggart
  • SVC-2489 - Votes: 18 - Group - Abilities - Parcel Powers - Always Allow 'Create Object' is being ignored. - Cheta Torok
  • SVC-391 - Votes: 11 - llEmail and llHTTPRequest do not handle non-ASCII characters - Omei Turnbull

Patches

Patches

Misc Pool

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/2009-03-30/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.