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

From Second Life Wiki
Jump to navigation Jump to search
Line 39: Line 39:
* {{jira|VWR-1165}} - get_cpu_clock_count() not portable on Linux. - {{User|Seg Baphomet}}
* {{jira|VWR-1165}} - get_cpu_clock_count() not portable on Linux. - {{User|Seg Baphomet}}


== General ==
=== General ===
* {{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}}
* {{jira|VWR-1171}} - Velocity interpolation causes weird physical behaviour client-side - {{User|Vernes Veranes}}
* {{jira|VWR-1171}} - Velocity interpolation causes weird physical behaviour client-side - {{User|Vernes Veranes}}

Revision as of 08:37, 13 June 2007


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

Invalid Issue IDs

  • VWR-602 - llInstantMessage is not sending emails - Azul Wilder
    • There is a note on sldev about this being an invalid issue ID, which could appear to be true since there is no indication that the LLID field was updated. A quick search of the LLIDs in jira that an already fixed issue, VWR-513, has the same issue ID. Dzonatas Sol 09:16, 13 June 2007 (PDT)
  • VWR-649 - Some items in Inventory won't rez since May 2 maintenance - Morgana Fillion
    • I moved the number that was in the reference field down to the comments. Dzonatas Sol 09:16, 13 June 2007 (PDT)

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. There is also a note on the Linden blog. Dzonatas Sol 09:01, 13 June 2007 (PDT)

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

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
  • MISC-285 - Objects owned by me cnt be used by others if the object rezzes objects to operate (ie poseballs) - LadyLutha Harlow
  • 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.