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

From Second Life Wiki
Jump to navigation Jump to search
Line 18: Line 18:
:* {{jira|VWR-2005}} - Votes: 0 - Unable to connect to SecondLife---DNS could not resolve host name, but i can see website fine. - {{User|goose bechir}}
:* {{jira|VWR-2005}} - Votes: 0 - Unable to connect to SecondLife---DNS could not resolve host name, but i can see website fine. - {{User|goose bechir}}


* {{jira|VWR-1922}} - Votes: 23 - Nearby Scripted Objects Glow Red While Editing. - {{User|Benja Kepler}}
* {{jira|VWR-718}} - Votes: 10 - Particles -> Slows to a trickle over time -> as of 1.15.x - {{User|Winter Ventura}}
* {{jira|VWR-718}} - Votes: 10 - Particles -> Slows to a trickle over time -> as of 1.15.x - {{User|Winter Ventura}}
* {{jira|MISC-501}} - Votes: 10 - Crashing during logging in - {{User|Annemie Lilliehook}}
* {{jira|MISC-501}} - Votes: 10 - Crashing during logging in - {{User|Annemie Lilliehook}}

Revision as of 11:23, 6 August 2007


Next meeting: 2007-08-06. Host: Rob Linden See Bug triage for details.

Fast Track Import

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

Already imported, but has a new solid repro, and I wrote a patch. Please update PJIRA and/or assign. Gigs Taggart


Hot by Vote

  • WEB-257 - Votes: 51 - Grid-Login and www.secondlife.com fails: DNS not resoved after ae-4-4.car2.SanFrancisco1.Level3.net - Jim Gustafson
  • SVC-364 - Votes: 7 - Downloaded and installed 1.17.1. Now can not log into SL. "Unable to connect to SL. DNS could not resolve the hostname. " - Chris Eggplant
  • VWR-2005 - Votes: 0 - Unable to connect to SecondLife---DNS could not resolve host name, but i can see website fine. - goose bechir

Patches


"Showstoppers"

  • MISC-517 - Votes: 0 - It will not me log in, it says a unknown error has occurred, and if it doesnt say that it says go to the website. - Chappelle Woller

Misc Pool

Sorted by priority. This probably isn't immediately useful, but we should figure out why it isn't, and figure out a community solution for making this a useful sort order.

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

Duplicate of bug already on triage agenda. Gigs Taggart
Can't repro. Not a showstopper at any rate. -- Rob Linden

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.
Retrieved from "https://wiki.secondlife.com/w/index.php?title=Bug_triage/2007-08-06&oldid=27443"