Bug triage/2008-06-16

From Second Life Wiki
< Bug triage
Revision as of 15:24, 16 June 2008 by Alexa Linden (talk | contribs) (→‎Hot by Vote)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


Next meeting: 2008-06-16 at 12 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

In QA, just needs to be associated with internal issue number Gigs Taggart
  • SVC-2426 - Votes: 19 - llPushObject in attachment pushing the person wearing it has stopped working with update 121 - darling brody
    • Asked if this is still a problem with the latest RC
  • SVC-1060 - Votes: 13 - Some parcels are not indexed in new search - Rifkin Habsburg
    • Asked if this is still a problem with the latest RC
  • VWR-7724 - Votes: 23 - Physical Objects fail to collide with Avatar at any appreciable Velocity - Kenn Nilsson
    • Resolved - Duplicate
  • WEB-510 - Votes: 11 - SLURL Map Contents Change According to the Map Zoom factor - leo Linden
    • Resolved - Duplicate
  • WEB-87 - Votes: 11 - Webmap Images not updating - Gigs Taggart
    • Imported - Assigned to Triage
  • SVC-126 - Votes: 13 - In world map image is not updating - Gigs Taggart
    • Closing again
  • VWR-3947 - Votes: 11 - Ugly font rendering in menu bar after upgrading to ATI drivers 7.12 - Geraldine Giha
    • Imported and finding out if we can do anything on this
  • SVC-2517 - Votes: 11 - ""Unable to create item that has caused problems on this region"" on Attachment - Jasper Yatsenko
    • Resolved - Duplicate of already imported issue - MISC-
  • SVC-2450 - Votes: 21 - An avatar sitting on an object whose root-prim is in a Safe area is invulnerable to damage when offset into a Damage-Enabled area - Jahar Aabye
    • Imported - Assigned to Mick Linden to see if he can Reproduce
  • SVC-1253 - Votes: 85 - users sitting on prims, which are set to phantom are not affected by damage. - Drew Dwi
    • Fix Pending

Patches

Patches

  • VWR-7708 - Votes: 1 - New constant PRIM_TEMPORARY - Strife Onizuka
    • Imported - Assigned to Triage
  • VWR-7606 - Votes: 0 - REGION_FLAGS_BLOCK_PUPPETEERING collides with REGION_FLAGS_BLOCK_PARCEL_SEARCH - Strife Onizuka
    • Leaving as-is
  • VWR-7362 - Votes: 1 - Add LSL constant EMPTY_KEY as (key)"""" please - meade paravane
    • Changed to Nice to Have

Misc Pool

Misc Pool

  • VWR-6207 - Votes: 1 - Build and Search floaters 'snap' downwards outside the viewer when dragged too low - Daedalus Young
    • Imported - Assigned to Triage

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/2008-06-16/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.