News is a little light coming out of the Lab on projects right now, although there was a blog post on things made on Monday, February 9th, which I also blogged about. However, new for the start of the week is still a little on the light side.
There are no scheduled server deployments for the week.
It had been anticipated that week #6 would see the Tools update project viewer (version 22.214.171.1248587) and the Avatar Hover Height project viewer (version 126.96.36.1998129) both superseded by a release candidate. However, neither update occurred.
It is possible these updates will occur during week #7; however, for the time being, all of the LL viewers remain as they were at the end of week #6, and as recorded in my Current Viewer Releases page, namely:
- Release version: 188.8.131.527623 (January 13th)
- Release candidate versions:
- Maintenance RC, version 184.108.40.2068030 – this has a number of issues associated with it, which may prevent its promotion to the de facto release viewer (January 27th)
- Experience Keys / Tools RC, version 220.127.116.118001 (January 14th) – this has been awaiting final server-side updates to the Experience capabilities
- Project viewers:
- Tool Update, version 18.104.22.1688587 (January 28th)
- Mesh importer, version 22.214.171.1248441 (February 3rd) – a number of bug reports have already been filed for this viewer – see the JIRA filter list for details.
- Avatar Hover Height, version 126.96.36.1998129 (January 21st)
- Viewer-managed Marketplace, version 188.8.131.526858 (November 19th, 2014)
- Oculus Rift project viewer, version 184.108.40.2065296 (October 13th, 2014).
Grid Status Page Relocated
As some have noticed, on Monday, February 9th, the Lab relocated the SL grid status page to a blog address, with a redirect from the “old” URL of status.secondlifegrid.net/.
However, the result has caused some confusion, notably as a result of breakage across sites and links referring to the “old” URL. Even some of the updates on the secondlife.com dashboard users see having been generating 404 errors as a result of the move.
Commenting on the change during the Simulator User Group meeting on Tuesday, February 10th, Simon Linden – who was out of the office when the change was made – said, “I don’t know what’s going to happen with the status page … but we know the shift caused issues … we heard a lot about it breaking things that relied on it. I’m not sure what the solution will be.”
So… watch that space…