Difference between revisions of "Bug triage/2008-08-11"

From Second Life Wiki
Jump to: navigation, search
(Fast Track Import)
(Misc Pool)
 
(One intermediate revision by the same user not shown)
Line 13: Line 13:
  
 
* {{jira|VWR-1740}} - Votes: 17 - Progressive increase in SL viewer memory footprint / decrease in performance when TPing between busy areas - {{User|Dael Ra}}
 
* {{jira|VWR-1740}} - Votes: 17 - Progressive increase in SL viewer memory footprint / decrease in performance when TPing between busy areas - {{User|Dael Ra}}
 +
** Asked hot long it takes for this issue to happen
 
* {{jira|SVC-1571}} - Votes: 22 - Rezzing a coalesced objects with 1024 scripted prims fails - {{User|Coral Gausman}}
 
* {{jira|SVC-1571}} - Votes: 22 - Rezzing a coalesced objects with 1024 scripted prims fails - {{User|Coral Gausman}}
 +
** Imported - Assigned to QA - Asked if Dev-15215 will fix this issue too
 
* {{jira|VWR-8337}} - Votes: 31 - Slows to 1 frame every 2 sec after login in the second time - {{User|skidz tweak}}
 
* {{jira|VWR-8337}} - Votes: 31 - Slows to 1 frame every 2 sec after login in the second time - {{User|skidz tweak}}
 +
** Last Triaged date added
 
* {{jira|VWR-5949}} - Votes: 14 - Out of Memory Error 1.19.1.2/3/4 - {{User|alan edelman}}
 
* {{jira|VWR-5949}} - Votes: 14 - Out of Memory Error 1.19.1.2/3/4 - {{User|alan edelman}}
 +
** Requested crash reports that are named to users so we can try to see a pattern between environments and crashes
 
* {{jira|VWR-7957}} - Votes: 11 - Clothing skinning error with nVidia 177.xx series drivers - {{User|Luna Hula}}
 
* {{jira|VWR-7957}} - Votes: 11 - Clothing skinning error with nVidia 177.xx series drivers - {{User|Luna Hula}}
 +
** Imported - assigned to QA
  
 
== Patches ==
 
== Patches ==
Line 25: Line 30:
  
 
* {{jira|SVC-2616}} - Votes: 1 - Torus refuses to accept 180 degree texture rotation - {{User|bau ur}}
 
* {{jira|SVC-2616}} - Votes: 1 - Torus refuses to accept 180 degree texture rotation - {{User|bau ur}}
 +
** Imported - Assigned to Core
 
* {{jira|VWR-8517}} - Votes: 0 - When moving from top to bottom, left and right eyes move in opposite directions. - {{User|Darena Bryant}}
 
* {{jira|VWR-8517}} - Votes: 0 - When moving from top to bottom, left and right eyes move in opposite directions. - {{User|Darena Bryant}}
 +
** Needs More Info
 
* {{jira|VWR-7483}} - Votes: 4 - Leg clothing layer meshes sometimes become stuck as ""flared"", erroneously full-length pants - {{User|Laila Kumaki}}
 
* {{jira|VWR-7483}} - Votes: 4 - Leg clothing layer meshes sometimes become stuck as ""flared"", erroneously full-length pants - {{User|Laila Kumaki}}
 +
**Imported - Assigned to Viewer
 
* {{jira|SVC-2611}} - Votes: 0 - Group invitation failed and spam mail of group invitation. - {{User|Naonao Watanabe}}
 
* {{jira|SVC-2611}} - Votes: 0 - Group invitation failed and spam mail of group invitation. - {{User|Naonao Watanabe}}
 +
**Imported - Assigned to QA
 
* {{jira|VWR-270}} - Votes: 12 - Event search searches only on the first word of an event's title - {{User|Samantha Poindexter}}
 
* {{jira|VWR-270}} - Votes: 12 - Event search searches only on the first word of an event's title - {{User|Samantha Poindexter}}
 +
** Relinked to DEV-3586
  
 
== Pre-meeting activity ==
 
== Pre-meeting activity ==

Latest revision as of 07:10, 12 August 2008


Next meeting: 2008-08-11 at 12 PM SLT at Hippotropolis Meeting areaD. See Bug triage for details.


Fast Track Import

  • VWR-3801 - Votes: 2 - In certain languages, parcel primitive usage is broken: displays only as 0 in About Land - bigmanu greene
    • Imported - Assigned to Viewer

Hot by Vote

High Voted Bugs

  • VWR-1740 - Votes: 17 - Progressive increase in SL viewer memory footprint / decrease in performance when TPing between busy areas - Dael Ra
    • Asked hot long it takes for this issue to happen
  • SVC-1571 - Votes: 22 - Rezzing a coalesced objects with 1024 scripted prims fails - Coral Gausman
    • Imported - Assigned to QA - Asked if Dev-15215 will fix this issue too
  • VWR-8337 - Votes: 31 - Slows to 1 frame every 2 sec after login in the second time - skidz tweak
    • Last Triaged date added
  • VWR-5949 - Votes: 14 - Out of Memory Error 1.19.1.2/3/4 - alan edelman
    • Requested crash reports that are named to users so we can try to see a pattern between environments and crashes
  • VWR-7957 - Votes: 11 - Clothing skinning error with nVidia 177.xx series drivers - Luna Hula
    • Imported - assigned to QA

Patches

Patches

Misc Pool

Misc Pool

  • SVC-2616 - Votes: 1 - Torus refuses to accept 180 degree texture rotation - bau ur
    • Imported - Assigned to Core
  • VWR-8517 - Votes: 0 - When moving from top to bottom, left and right eyes move in opposite directions. - Darena Bryant
    • Needs More Info
  • VWR-7483 - Votes: 4 - Leg clothing layer meshes sometimes become stuck as ""flared"", erroneously full-length pants - Laila Kumaki
    • Imported - Assigned to Viewer
  • SVC-2611 - Votes: 0 - Group invitation failed and spam mail of group invitation. - Naonao Watanabe
    • Imported - Assigned to QA
  • VWR-270 - Votes: 12 - Event search searches only on the first word of an event's title - Samantha Poindexter
    • Relinked to DEV-3586

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-08-11/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.