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

From Second Life Wiki
Jump to navigation Jump to search
Line 36: Line 36:


=== General ===
=== General ===
* {{jira|SVC-171}} - Objects in a user's inventory show 00000-00-00-00000 for UUIDs when tried to attach - {{User:Montana Corleone}}
* {{jira|SVC-171}} - Objects in a user's inventory show 00000-00-00-00000 for UUIDs when tried to attach - {{User|Montana Corleone}}
** IM'd Montana. This was one that has more votes on the issue it marks as duplicate (but misfiled). Objects still exist and can repro. [[User:Dzonatas Sol|Dzonatas Sol]] 21:18, 14 June 2007 (PDT)
** IM'd Montana. This was one that has more votes on the issue it marks as duplicate (but misfiled). Objects still exist and can repro. [[User:Dzonatas Sol|Dzonatas Sol]] 21:18, 14 June 2007 (PDT)
* {{jira|VWR-1172}} - SLVoice.exe crash on startup -  .111 and .112  - {{User|Mosley Jewell}}
* {{jira|VWR-1172}} - SLVoice.exe crash on startup -  .111 and .112  - {{User|Mosley Jewell}}

Revision as of 07:39, 15 June 2007


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


Issues

  • Empty

Tabled Issues -- Feel free to Vote on these!

Invalid Issue IDs

  • VWR-895 - Texture latency - texturing all sides of a prim at once results in one side not being textured, has to be selected individually - Cory Edo
    • I IM'd Cory to see if issue can still be reproduced. Moved old refs out of LLIID and into comments. Dzonatas Sol 08:04, 15 June 2007 (PDT)
  • MISC-285 - Objects owned by me cnt be used by others if the object rezzes objects to operate (ie poseballs) - LadyLutha Harlow
    • I IM'd LadyLutha and asked for more specific steps to attempt reproduction. Dzonatas Sol 08:13, 15 June 2007 (PDT)
  • SVC-277 - Clearing trash in inventory crashes viewer - Emilly Orr
  • VWR-708 - Crash -> Viewer Update -> Download Option - sarika fizgig
  • VWR-918 - Chat/IM display width is small - Kilmarac Drago
  • MISC-86 - Dataserver Events appear to not be working - EDIT: (with notecards that had previously had inv items in them) - Snaptick Laxness
  • MISC-183 - Difficulties responding to group im's and tp'ing to events in response to tp's sent out. - Ima Peccable
  • VWR-404 - Local Lighting strobes, especially on shiney and curved surfaces. - Nobody Fugazi
  • VWR-487 - female upper body muscle settings do not save/load correctly - Yuriko Nishi

New Patches

General


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.