Difference between revisions of "User:Opensource Obscure/JIRA"

From Second Life Wiki
Jump to navigation Jump to search
m (Linux Viewer 3.0.1 Beta crash, Minidump file is empty)
m (-)
Line 95: Line 95:


==misc==
==misc==
* https://jira.secondlife.com/browse/VWR-2950 Group Notices and Group IMs Constantly Malfunctioning
* https://jira.secondlife.com/browse/SVC-1509 Error message when starting and posting to a group IM session
* https://jira.secondlife.com/browse/VWR-26648 ''Early Beta Test Issues - v3.0.0''
* https://jira.secondlife.com/browse/VWR-26648 ''Early Beta Test Issues - v3.0.0''
* https://jira.secondlife.com/browse/SVC-5387 Snapshot to postcard failure
* https://jira.secondlife.com/browse/SVC-5387 Snapshot to postcard failure

Revision as of 05:06, 23 August 2011

User page - JIRA - Interests - Groups - LSL - Places - Stores - Translations - other pages



This is some JIRA stuff I'm currently focusing on. Mostly a personal scrapbook page.

UI (User Interface)

Social

new features

camera/rendering

avatar

shortcuts

persistency of settings / logs

Linux misc

Also see > Social > https://jira.secondlife.com/browse/WEB-3997 (Linux) Login Screen: direct teleport to suggested locations broken when region name has 2 or more words

misc

textures loading

  • https://jira.secondlife.com/browse/VWR-24191 Meta-Issue: Poor texture loading and freezes indicate larger chain of bugs: small texture not loaded. Texture frequently shows grey when running script that cycles thru 5 textures with a llSleep(1.3) between each. Using "texture name" and storing the five textures in CONTENTS fails the same as using the UUID of the texture. Running the same script as above but on a regular prim (instead of a sculpt) and with a sleep of 10 seconds between each texture change – produces similar failure. (Texture shows as grey or blurred on ocassions but frequently enough).

test plans

meta issues

Durante lo Scrum Daily Meeting di oggi (4 May 2011), Grumpity e Oz hanno spiegato che a lungo andare i Meta Issues diventano inutili per Linden Lab. A differenza di un crash bug che può venire affrontato, risolto e chiuso, i Meta Issues rimangono aperti indefinitamente. [Meta Issues have limited long-term value to Linden Lab]

presi in considerazione, fix pending, etc