Difference between revisions of "Beta/BlueSteel"

From Second Life Wiki
Jump to navigation Jump to search
Line 1: Line 1:
{{TOCright}}
= What is BlueSteel? =
= What is BlueSteel? =
BlueSteel 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. BlueSteel 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/LeTigre|LeTigre]] and [[Beta/Magnum|Magnum]]. These can and probably will change on a weekly basis.
BlueSteel 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. BlueSteel 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/LeTigre|LeTigre]] and [[Beta/Magnum|Magnum]]. These can and probably will change on a weekly basis.

Revision as of 10:18, 26 October 2010

What is BlueSteel?

BlueSteel 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. BlueSteel 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 LeTigre and Magnum. These can and probably will change on a weekly basis.

BlueSteel Release Channel

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

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.

Additional Info

BlueSteel can be on about 10% of the grid. These 4 regions will always have the latest up to date BlueSteel 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.

  1. BlueSteel Sandbox 1
  2. BlueSteel Sandbox 2
  3. BlueSteel Sandbox 3
  4. BlueSteel Sandbox 4

How To File Bugs

  1. https://jira.secondlife.com/secure/CreateIssue.jspa?pid=10002&issuetype=1
  2. Log in.
  3. Choose "Affects Version/s" that matches the server version from "Help->About Second Life..."
  4. Be verbose and descriptive.
  5. Be sure to add your environment.

Release Notes

10.12.31.218124

  • "Encroachment" project: 2011-01-05
  • Bug Fix / Feature
    • Ability to return objects that overlap ("encroach") on a parcel.
      Depends on future viewer modifications. More details on how this works (here).

10.12.13.216725

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

10.12.06.216207

  • "Compression" project deployed: 2010-12-08
  • Features
    • Compress region crossing data
      Avatar data is compressed when moving/TPing from one region to another. This should decrease the amount of time it takes to move between regions.
      This feature will be disabled at initial deploy, and enabled via a config change later.
  • Bug Fixes
    • SVC-6556: Avatar and the ship sails attached to the avatar do not rez beyond 80 meters
    • Simulator crash fixes

10.11.12.214623

  • "Linkability" project deployed: 2010-11-17
  • Bug Fixes

10.11.03.213781

10.10.25.213013

10.10.20.212648

  • Deployed: 2010-10-20
  • Bug Fixes:
    • Simulator crash fix
    • Internal tools updates relating to content management

10.10.11.211793

  • Deployed: 2010-10-13
  • Bug Fixes:
  • SVC-6063: Object doesn't appear in Inventory when taken while frozen by grey goo fence
  • Simulator does not preserve static objects' CRC values upon restart
    This makes objects have to re-download after a sim restart, instead of pulling from cache.
  • Faster terrain collisions
  • Simulator crash fix

10.09.21.210146

10.10.05.211372

  • 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

  • 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.

10.09.21.210146

  • Deployed: 2010-09-22
  • Bug Fixes:
    • Simulator crash modes
    • Improvements to the Region Conductor
      This helps down regions come back up more quickly.
    • Modifications to deploy tools to support Release Candidates

10.9.10.209504

  • Promoted to AGNI Release 2010-09-21

Bug fixes:

  • Several simulator crash modes