Bug triage/2007-07-09

From Second Life Wiki
< Bug triage
Revision as of 23:59, 8 July 2007 by Gigs Taggart (talk | contribs) (went over them)
Jump to navigation Jump to search


Next meeting: 2007-07-09. See Bug triage for details.

Fast Track Import

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

  • VWR-1400 - Votes: 12 - Inventory's Recent Items tab settings should persist across logins - Be Holder
Looks clean for re-importation. Gigs Taggart

Hot by Vote

  • MISC-378 - Votes: 42 - Linked Media on land (audio stream & video stream) can be viewable to anyone with "View Admin Options" on. Media Links in parcels should be PRIVATE ALWAYS. - Doubledown Tandino
Recommend WONTFIX, DRM/Copybot type issue. No way to protect this. VWR-1059 is similar, was closed by LL on the same grounds that it would require some kind of DRM arms-race, or only be an illusion of security.
  • SVC-273 - Votes: 11 - Items sold at vendors are sometimes ending up full permissions - Angel Lamar
This must be very rare if it is happening. I IM Stroker to see what he means by having "Seen it first hand" Gigs Taggart 00:19, 9 July 2007 (PDT)

Reopened issues

This week's theme: reopened issues.

This one seems to have a solid repro now, I spoke with someone experiencing it and we worked together on a repro. See comments. Gigs Taggart 00:59, 9 July 2007 (PDT)
Not sure why this one was reopened, or if the linden just forgot to close it. Gigs Taggart


Patches


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

  • WEB-18 - Votes: 1 - Transaction History not showing recent transactions - Nowun Till
No comment was left when it was reopened, and it's an ancient bug. Gigs Taggart 00:59, 9 July 2007 (PDT)
Another "copybot" type whine. Linden Lab has already stated this is WONTFIX.

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.