Difference between revisions of "Linden Lab Official:Known Issues"

From Second Life Wiki
Jump to: navigation, search
m (1 revision)
(Revised Parature import)
(2 intermediate revisions by the same user not shown)
(No difference)

Revision as of 16:13, 6 October 2009

Ll color vert 100.gif
Official Linden Lab® Information: You may access and link to this page, but you may not copy, distribute, modify, adapt, or translate any content on this page. This content is subject to the Terms of Service and is not available under the Creative Commons or any other license.

Have a suggestion to improve this page? Contact us.

This article describes how to navigate the Second Life Known Issues page, which is a semi-automatically updated page describing known issues for non-beta releases.

The Second Life Known Issues page contains issues Linden Lab has verified as in the current release and Safe for Public*.

KBwarning.png Warning: %%

This is not a complete list of bugs in Second Life. |}

Here's what each term or icon means:

  • Priority Key: This is the priority we've assigned to each bug. The priority is gauged by the following. It is not uncommon for bugs to be up/downgraded in priority throughout their lifespans.
  • Kbext priority blocker.gif Showstoppers are must-fixes for the next release version that cause Second Life to be completely unusable for the majority of residents.
  • Kbext priority critical.gif Criticals are should-fixes (but not guaranteed to be fixed) for the next release version.
  • Kbext priority major.gif Majors are bugs that we acknowledge as bad but usually have a known workaround, or are less critical to fix because they affect a minority of residents. We still feel these are important and we try to get them fixed in each major point release.
  • Kbext priority minor.gif Normals are bugs that do not hinder use of Second Life but are annoying nonetheless.
  • Kbext priority trivial.gif Smalls are bugs that we consider pretty low on the totem pole.
  • Issue (SL) Number: This is the internal key (SL-#) of an issue. Linden Lab uses an issue tracking system company-wide, so these numbers tend to be all over the map. The SL-# does not in any way indicate how many bugs are in Second Life!
  • Short Bug Description: This is a short description meant to allow quick scanning of the page for a specific issue. They are written tersely and usually modified by QA before posting.
  • Affects: This indicates which version(s) of the Second Life client this bug has been verified in, and what key components are affected (in parentheses).
  • Show Repro: Click this for instructions on how to reproduce the bug. Following these steps should result in the Observed Results. We usually put the Expected Results here as well.

* Safe for Public bugs are any non-exploit** issue that either hinders use of Second Life, results in unexpected behavior, or otherwise negatively impacts Resident experiences inworld. Safe for Public bugs are reproducible by Residents. An example of a bug we would not list would be a bug in simulator code that negatively impacts the Resident experience, but isn't Resident-reproducible. ** Exploits are bugs that could be used to get an advantage over others, unauthorized access to scripts, unauthorized copying, transferring or modifying of objects that you didn't create (also called 'permissions' bugs) and other bugs that could potentially cause a comprimise of the grid or a Resident's privacy. We take exploits very seriously, but we don't list them in the Known Issues page. If you have an exploit bug, please report it and contact a liaison or an officer of the Bug Hunters group with the RT# you're given by the auto-response email. (see also: How to Report a Bug)