2008-04-02 1:48am PST: Completed
2008-04-02 1:15am PST: 90% completed
2008-04-01 12:25pm PST: 70% completed
2008-04-01 11:00pm PST: 40% completed
2008-04-01 10:00pm PST: 30% completed
2008-04-01 8:30pm PST: Code distribution complete, rolling restarts beginning
What Were The Results Of Yesterday’s Initial Deploy?
Last evening we rolled out the new simulator to 1575 regions across Second Life, and today we have been evaluating the early results. A surprisingly small number of bugs were reported, with none of them serious enough to cause us to hold off on the rest of the deploy. I credit this early result to the hard work of the many resident beta testers who were deeply involved in the Early Adopter process for months, as well as the over 600 region owners who opted in to beta test the simulator on their regions on Second Life. Hopefully as we complete the rollout we will continue to see mostly minor issues, with the benefit of a noticeably lower simulator crash rate.
The team is already working on the issues discovered since the initial deploy. We are tentatively expecting to do a first update next week to resolve the highest priority issues seen during the intial rollout phase.
As I’ve said before, we expect that you may find some other oddities, and will be actively working new issues as they appear, and are prepared to do short-cycle updates as we resolved these issues.
When Will The Completion Rollout Happen?
Tonight, starting at approximately 7:00 pm PST (19:00 PST), we will begin the deploy cycle to do a rolling restart across the rest of Second Life to update to the new 188.8.131.52683 simulator. This rollout will likely take five or six hours to complete.
By the end of this process, all Second Life simulators will be running Second Life Server v184.108.40.206683.
How Do I Know That My Region Has Been Updated?
Open Help > About Second Life… If the fourth text line reads “Second Life Simulator 220.127.116.11683”, then your region has completed the rolling restart and has been updated.
Why Did You Not Post The Release Schedule Earlier?
There were some other systems issues that needed to be taken care of before we could know when the deploy would actually start, and I was holding to see when those issues had been fully resolved. It did not seem prudent to commit to a deploy start on the blog until it seemed that the other issues had been resolved.
Rather than post a series of “delay/reschedule” notes, I decided to hold posting until we were sure that we were ready to start the deploy process, and that it would actually happen tonight. My apologies that this created a bit of a “vacuum” of information about the completion of the deploy process.
Remember… We’re Still Here
Although we have done a very large scale Early Adopter Program, which included over a million hours of simulator run time, we know that you may find some scripts that do not behave quite the same, vehicles that may drive differently or other slight differences in this release. We are still here and will continue to work issues as they arise.
Public Office Hours
We will be continuing to hold open office hours in-world to discuss any issues, reviewing bug reports on the public jira, and fixing critical issues as quickly as we can. Office hours provide you the chance to talk directly with the software development team about issues you may have found, demonstrate problems, and discuss on-going strategy questions. Please feel free to drop in, even if you are not a “hard core developer”.
Office hours are held on:
Tuesdays at 11:00-12:00 PST
Thursdays at 17:00-18:00 PST (5:00 – 6:00 PM PST)
At the center of the region “Content to Hover”
Havok4 Program Manager