Bug triage/2008-06-16
From Second Life Wiki
QA Portal > Bug triage > Bug triage/2008-06-16
Next meeting: 2008-06-16 at 12 PM SLT at Hippotropolis Meeting area. See Bug triage for details.
Contents |
Fast Track Import
(Move bugs here that have solid repros, or valid patches that you have reviewed)
Hot by Vote
- SVC-2462[c] - Votes: 12 - External email to LSL scripts failing 100% of the time - Apotheus Silverman
- Imported - Assigned to Vektor Linden
- VWR-7474[c] - Votes: 11 - Frequent hanging - Timothy Oconnell
- SVC-2333[c] - Votes: 14 - Traffic numbers reset to 0 - Dilbert Dilweg
- Imported - Assigned to Triage
- SVC-2443[c] - Votes: 22 - Flight Very Difficult - Stuck in Hover - Flaran Riggles
- In QA, just needs to be associated with internal issue number Gigs Taggart
- SVC-2426[c] - 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[c] - 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[c] - Votes: 23 - Physical Objects fail to collide with Avatar at any appreciable Velocity - Kenn Nilsson
- Resolved - Duplicate
- WEB-510[c] - Votes: 11 - SLURL Map Contents Change According to the Map Zoom factor - leo Linden
- Resolved - Duplicate
- WEB-87[c] - Votes: 11 - Webmap Images not updating - Gigs Taggart
- Imported - Assigned to Triage
- SVC-126[c] - Votes: 13 - In world map image is not updating - Gigs Taggart
- Closing again
- VWR-3947[c] - 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[c] - 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[c] - 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[c] - Votes: 85 - users sitting on prims, which are set to phantom are not affected by damage. - Drew Dwi
- Fix Pending
Patches
- VWR-7708[c] - Votes: 1 - New constant PRIM_TEMPORARY - Strife Onizuka
- Imported - Assigned to Triage
- VWR-7606[c] - Votes: 0 - REGION_FLAGS_BLOCK_PUPPETEERING collides with REGION_FLAGS_BLOCK_PARCEL_SEARCH - Strife Onizuka
- Leaving as-is
- VWR-7362[c] - Votes: 1 - Add LSL constant EMPTY_KEY as (key)"""" please - meade paravane
- Changed to Nice to Have
Misc Pool
- VWR-6207[c] - 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:
- Copy the markup from Template:Triage Template as a starting point for your agenda. One wiki trick you can employ is to save "{{subst:Triage Template}}" as the complete markup of a new page. Doing this is the equivalent of copying and pasting the full markup of the template in.
- Look at the results of one of these queries
- General triage: "Bugs, sorted by LL ID"):
- UI triage:
- (Note: there's no hard and fast rule that says these are the only valid queries. If you feel there's a better query one particular week, use that.)
- Save a copy of the XML version of the query
- Run this perl script on the xml file
#!/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 "* {{jira|$key}} - Votes: $votes - $title - {{User|$reporter}}\n"; }
- Pick a reasonable cutoff point, and copy the output into the appropriate section of your newly created page.

