Difference between revisions of "Bug triage/2007-06-18"

From Second Life Wiki
Jump to navigation Jump to search
(→‎General: Commented)
Line 11: Line 11:


* {{jira|VWR-537}} - Black/test/etc. textures appearing at random - {{User|Marianne McCann}}
* {{jira|VWR-537}} - Black/test/etc. textures appearing at random - {{User|Marianne McCann}}
** There is a hint that an older issue exists. [[User:Dzonatas Sol|Dzonatas Sol]] 09:01, 13 June 2007 (PDT)
* {{jira|SVC-308}} - When Trying To Connect To SL I Get "Unable To Connect To A Simulator" - {{User|Kevin Paisley}}
* {{jira|SVC-308}} - When Trying To Connect To SL I Get "Unable To Connect To A Simulator" - {{User|Kevin Paisley}}
 
** Appears to be a support issue, I didn't see a note if anyone that tried to contact support. [[User:Dzonatas Sol|Dzonatas Sol]] 09:01, 13 June 2007 (PDT)


== Issues tabled due to lack of votes (hint: not ready for triage) ==
== Issues tabled due to lack of votes (hint: not ready for triage) ==

Revision as of 08:01, 13 June 2007


Next bug triage - Monday, 3pm at Rob Linden's office in Grasmere🖈

Invalid Issue IDs

General

  • VWR-537 - Black/test/etc. textures appearing at random - Marianne McCann
    • There is a hint that an older issue exists. Dzonatas Sol 09:01, 13 June 2007 (PDT)
  • SVC-308 - When Trying To Connect To SL I Get "Unable To Connect To A Simulator" - Kevin Paisley
    • Appears to be a support issue, I didn't see a note if anyone that tried to contact support. Dzonatas Sol 09:01, 13 June 2007 (PDT)

Issues tabled due to lack of votes (hint: not ready for triage)


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.