Unfortunately, the clock change in the UK / Europe meant I was unable to make the Simulator User Group meeting on Tuesday, October 30th.
Server Deployment Plans
As always, please refer to the server deployment thread for the latest news and updates.
- There was no deployment to the SLS (Main) channel on Tuesday, October 30th, nor was the channel restarted. It remains on server release 18#18.10.04.520268, comprising internal fixes.
- On Wednesday, October 31st, 2018, the RC channels should be updated as follows:
There have been two SL viewer updates to start the week:
- The Spotykach Maintenance RC viewer updated to version 220.127.116.110686 on October 31st.
- The Bakes on Mesh project viewer updated to version 18.104.22.1680711 on October 29th.
The remaining viewers in their pipelines remain unchanged from week #43:
- Current Release version 22.214.171.1249298, dated September 5th, promoted September 26th. Formerly the Rakomelo Maintenance RC viewer – No change.
- Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
- Animesh RC viewer, version 126.96.36.1990636, October 18th.
- Estate Access Management (EAM) RC viewer, version 188.8.131.520057, September 28th.
- BugSplat RC viewer, version 184.108.40.2069462, September 10. This viewer is functionally identical to the current release viewer, but uses BugSplat for crash reporting, rather than the Lab’s own Breakpad based crash reporting tools.
- Love Me Render RC viewer, version 220.127.116.118751, released on August 20.
- Project viewers:
- Linux Spur viewer, version 18.104.22.1689906, dated November 17th, 2017 and promoted to release status 29th November – offered pending a Linux version of the Alex Ivy viewer code.
- Obsolete platform viewer, version 22.214.171.1240847, May 8th, 2015 – provided for users on Windows XP and OS X versions below 10.7.
As most are aware, Sunday saw some significant issues with Second Life, with users in particular have log-in issues.
It appears the problems were directly the result of a prolonged / vicious distributed denial of service (DDOS) attack, as April Linden confirmed in the forums, stating:
I can confirm it was a DDoS attack, and yes, the folks on my team had a rough weekend.
We do our best to fight DDoSes, but this one took quite a bit more effort than normal.
I’m sorry people’s plans got interrupted over the weekend. It was a rough weekend for all of us… including those of us on this side of the grid, too.
I’ve no idea if there will be a more formal blog post on the matter or not.