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

From Second Life Wiki
Jump to navigation Jump to search
(if you close or resolve them, take them off the list)
(→‎New Patches: VWR-424 resolved)
Line 27: Line 27:
** Strife has posted a new patch. I'll leave this here just for votes. [[User:Dzonatas Sol|Dzonatas Sol]] 08:40, 15 June 2007 (PDT)
** Strife has posted a new patch. I'll leave this here just for votes. [[User:Dzonatas Sol|Dzonatas Sol]] 08:40, 15 June 2007 (PDT)
* {{jira|VWR-424}} - Crashes shortly after login. - {{User|Bunny Mayne}}
* {{jira|VWR-424}} - Crashes shortly after login. - {{User|Bunny Mayne}}
** Resolved as fixed. I referred those with newer issues to meta-issue VWR-521 for more help. [[User:Dzonatas Sol|Dzonatas Sol]] 12:23, 15 June 2007 (PDT)
* {{jira|VWR-654}} - Tools / Reset all Scripts in Selection Window does not Scroll automatically - {{User|Zi Ree}}
* {{jira|VWR-654}} - Tools / Reset all Scripts in Selection Window does not Scroll automatically - {{User|Zi Ree}}
* {{jira|VWR-893}} - Patch to make View Admin Options sticky - {{User|Gigs Taggart}}
* {{jira|VWR-893}} - Patch to make View Admin Options sticky - {{User|Gigs Taggart}}

Revision as of 11:23, 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)
    • Cory demo'd it to me. All the textures change on all sides, but the one side then reverts back. Dzonatas Sol 09:56, 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)
  • VWR-918 - Chat/IM display width is small - Kilmarac Drago
  • MISC-183 - Difficulties responding to group im's and tp'ing to events in response to tp's sent out. - Ima Peccable
    • I IM'd Ima. This is from May 2nd, so it probably was from the upgrade traffic. Dzonatas Sol 11:54, 15 June 2007 (PDT)

New Patches

  • SVC-104 - llBase64ToInteger caveats & bugs - Strife Onizuka
    • Is there a new patch since it was imported? Dzonatas Sol 09:39, 13 June 2007 (PDT)
    • Strife has posted a new patch. I'll leave this here just for votes. Dzonatas Sol 08:40, 15 June 2007 (PDT)
  • VWR-424 - Crashes shortly after login. - Bunny Mayne
    • Resolved as fixed. I referred those with newer issues to meta-issue VWR-521 for more help. Dzonatas Sol 12:23, 15 June 2007 (PDT)
  • VWR-654 - Tools / Reset all Scripts in Selection Window does not Scroll automatically - Zi Ree
  • VWR-893 - Patch to make View Admin Options sticky - Gigs Taggart
  • VWR-1109 - Some source files in *.zip source distribution contain lines that end with LF only - Alissa Sabre
    • probably fixed already with 1.17. (NB)
  • VWR-1140 - About Land floater is not resizable, ban and access lists too small - Zi Ree
  • VWR-1165 - get_cpu_clock_count() not portable on Linux. - Seg Baphomet

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.