Revision as of 12:25, 12 October 2010

What is LeTigre?

LeTigre is the nickname for 1 of our 3 'Server Release Candidate' channels. When a new version of server is ready for the main grid it needs to prove itself in a release candidate channel for one week first. This is what we used to call a pilot roll. Once a 'Server Release Candidate' has proven itself it will be rolled out to the entire main grid. LeTigre will then be given a new 'Server Release Candidate'. We might have as many as three 'Server Release Candidate' channels on the main grid at the same time. The others are BlueSteel and Magnum. These can and probably will change on a weekly basis.

LeTigre Release Channel

This is the LeTigre Release Channel. Information on this release candidate is below. For more information on beta projects, see: Beta Server Office Hours.

Overview

LeTigre is currently running the same code as BlueSteel.

Timeframe

Release Notes

10.12.31.218123

"Simulator Shutdown" project: 2011-01-05
Features
- Addresses back-end issues to make simulator/region restarts faster and more reliable.

10.12.10.216629

Update to "Maint Server" project, deployed 2010-12-14
Bug Fixes
- SVC-6604: Objects from Inventory silently fail to rez

10.12.06.216172

"Maint Server" project scheduled: 2010-12-08
Bug Fixes
- SVC-6556: Avatar and the ship sails attached to the avatar do not rez beyond 80 meters
- Simulator crash fixes

10.11.30.215699

"Maint Server" Deployed: 2010-12-01
Features:
- Scripts now have access to server version
  Ex: llSay(0,llGetEnv("sim_channel") + " " + llGetEnv("sim_version"));
- Region admins have greater access to script usage info
  - The following constants have been added for use with llGetObjectDetails:
    - OBJECT_RUNNING_SCRIPT_COUNT: Returns the number of running scripts on the object
    - OBJECT_TOTAL_SCRIPT_COUNT: Returns the total number of scripts, running or not, on the object
    - OBJECT_SCRIPT_MEMORY: Returns the total script memory used by the object
Bug Fixes:
- SVC-6332: llLinkParticleSystem() causes the avatar to emit particles until a relog
- SVC-5908: Setting VEHICLE_HOVER_HEIGHT to values > 1024 fails to work as intended
- SVC-6204: Group members still being charged group liability for "parcel directory fee" for land on disabled regions
- SVC-6367: Grey goo fence prevents objects from going off world

10.11.09.214391

Deployed: 2010-11-10
Update to #10.11.03.213725
Integrating the project from BlueSteel

10.11.03.213725

Deployed: 2010-11-03
Features
- "Threaded Rez": Object rezzing is moved to a separate thread.
  This should minimize lag instances when complex objects are rezzed in a region.
Bug Fixes
- SVC-6399: Online friends not showing online
- SVC-6430: Objects de-render behind you when you look away.

10.10.20.212725

Deployed: 2010-10-25
Update to #10.09.27.210681

Bug Fixes
- Simulator crash fix

10.10.13.211971

Rolled back to #10.10.05.211474: 2010-10-13

~~Deployed to LeTgire: 2010-10-13~~

~~Update to #10.09.27.210681~~

~~Bugs Fixed~~
- ~~Several server crash modes fixed~~

10.10.05.211474

Deployed: 2010-10-07
Update to #10.09.27.210681

Bug Fixes
- In-world land and L$ purchases failing due to lost session information

10.10.05.211372

Deployed: 2010-10-06
Update to #10.09.27.210681

Bug Fixes
- SVC-6368: llRequestAgentData DATA_ONLINE - intermittent failure
- Simulator crash fixed
- Simulator restart failure fixed
  This caused regions to be down for extended periods of time during the previous rolling restart

10.09.27.210805

Deployed: 2010-09-29
Update to #10.09.27.210681

Bug Fixes
- Simulator crash regression fixed

10.09.27.210681

Deployed: 2010-09-29

Features
- Enable tcmalloc-1.6 by default to help with memory and performance debugging.
- Simulator disk operations moved into threads for performance reasons.
Bug Fixes
- SVC-583: Five minute wait due to "System Logging You Out" happens every time when wearing scripted attachments.
- Several stuck presence issues resolved.

Test Plans

Additional Info

"LeTigre is soft yet deadly--- just like the tigers of France."

LeTigre can be on about 10% of the grid. These 4 regions will always have the latest up to date LeTigre RC code. You are welcome to use them as needed. They are available to members of the group "Second Life Beta". Please join this group: http://world.secondlife.com/group/19657888-576f-83e9-2580-7c3da7c0e4ca

If they are closed that means there is no RC using that channel.

LeTigre Sandbox 1
- http://slurl.com/secondlife/LeTigre%20Sandbox%201/128/128/25
LeTigre Sandbox 2
- http://slurl.com/secondlife/LeTigre%20Sandbox%202/128/128/25
LeTigre Sandbox 3
- http://slurl.com/secondlife/LeTigre%20Sandbox%203/128/128/25
LeTigre Sandbox 4
- http://slurl.com/secondlife/LeTigre%20Sandbox%204/128/128/25

How To File Bugs

http://jira.secondlife.com/secure/CreateIssue!default.jspa
Log in.
Select Project: "2. Second Life Service - SVC"
Select Issue Type: "Bug"
Click Next.
Choose "Affects Version/s" that matches the server version from "Help->About Second Life..."
Be verbose and descriptive.
Be sure to add your environment.

@@ Line 1: / Line 1: @@
+{{TOCright}}
 = What is LeTigre? =
 LeTigre is the nickname for 1 of our 3 'Server Release Candidate' channels. When a new version of server is ready for the main grid it needs to prove itself in a release candidate channel for one week first. This is what we used to call a pilot roll. Once a 'Server Release Candidate' has proven itself it will be rolled out to the entire main grid. LeTigre will then be given a new 'Server Release Candidate'. We might have as many as three 'Server Release Candidate' channels on the main grid at the same time. The others are [[Beta/BlueSteel|BlueSteel]] and [[Beta/Magnum|Magnum]]. These can and probably will change on a weekly basis.

Difference between revisions of "Beta/LeTigre"