Difference between revisions of "Beta/Magnum"
Oskar Linden (talk | contribs) |
Oskar Linden (talk | contribs) |
||
| Line 9: | Line 9: | ||
== Timeframe == | == Timeframe == | ||
We will normally roll Release Candidates to the grid Wednesday mornings when we have them. If we don't have one we won't roll anything. The RC has to be stable on the main grid for 6 days. If so it will be rolled to the full grid next the next Tuesday morning. During the course of the 6 days RC cycle regions on the RC cycle may be restarted more frequently. | |||
== Release Notes == | == Release Notes == | ||
Revision as of 08:41, 13 October 2010
What is Magnum?
Magnum 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. Magnum 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 LeTigre. These can and probably will change on a weekly basis.
Magnum Release Channel
This is the Magnum Release Channel. Information on this release candidate is below. For more information on beta projects, see: Beta Server Office Hours.
Overview
Magnum is unused at this time.
Timeframe
We will normally roll Release Candidates to the grid Wednesday mornings when we have them. If we don't have one we won't roll anything. The RC has to be stable on the main grid for 6 days. If so it will be rolled to the full grid next the next Tuesday morning. During the course of the 6 days RC cycle regions on the RC cycle may be restarted more frequently.
Release Notes
10.12.13.216725
- Released: 2011-01-05
- Features
- Running same code as main channel (Second Life Server release notes)
- Compression feature enabled
- This compresses the data sent between regions when teleporting or crossing region boundaries. During this RC phase, it will only show improvement when going between two Magnum regions.
10.11.30.215699
- Deployed: 2010-12-08
- Deployed code from the main channel (Second Life Server release notes)
10.11.09.214391
- Deployed: 2010-11-17
- Same code as main channel
- Using new Inventory API backend-service
10.11.09.214282
- Deployed: 2010-11-10
- Sims running same code as main channel
- Using new Inventory API backend-service
- Bug Fixes
- SVC-6503: A folder with one or more items currently worn will not show the un-worn items also in that folder
10.11.03.213721
- Deployed: 2010-11-03
- Features
- Enable tcmalloc-1.6 by default to help with memory and performance debugging.
- Simulator disk operations moved into threads for performance reasons.
- Inventory Capabilities are enabled.
- Bug Fixes
- Known Issues
10.10.25.213029
- Deployed: 2010-10-26
- Running same code as main channel, see Release_Notes/Second_Life_Server/10#10.10.18.212360
- Additionally, Display Names configuration is enabled.
10.09.21.210146
- Deployed: 2010-09-28
- Running the same code as the main channel, see Release_Notes/Second_Life_Server/10#10.09.21.210146
Test Plans
Additional Info
"You gotta tame the beast before you let it out of its cage."
Magnum can be on about 10% of the grid. These 4 regions will always have the latest up to date Magnum 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.
- Magnum Sandbox 1
- Magnum Sandbox 2
- Magnum Sandbox 3
- Magnum Sandbox 4
How To File Bugs
- https://jira.secondlife.com/secure/CreateIssue.jspa?pid=10002&issuetype=1
- Log in.
- Choose "Affects Version/s" that matches the server version from "Help->About Second Life..."
- Be verbose and descriptive.
- Be sure to add your environment.