Server Deployments – Recap
As always, please refer to the server deployment thread for updates.
- There was no deployment to the Main (SLS) channel on Tuesday, February 21st, again leaving it on release 17#17.01.27.323172. However, all regions on the channel were restarted in keeping with the Lab’s policy of restarting a channel every other week, regardless as to whether or not it has received a deployment update.
- On Wednesday, February 22nd, all thee RC channels received a new server maintenance package containing “minor” changes. No release notes available.
RC Release E-mail Issue
One of the changes on the RC release is to increase privacy protection on e-mails – which is a good thing. However, it now means that the viewer is performing a check it doesn’t need to do, and as a result, sending snapshots to e-mail ((aka “postcards”) can fail or encounter problems.
There is a viewer-side fix for this in the works, but it has yet to clear LL’s QA, but will be appearing in a viewer once it has. It also means that all viewers which do not have the fix can encounter issues when trying to send snapshots to e-mails, and so will also have to include the fix as well.
No further updates this week, leaving the various pipelines as:
- Current Release version: 220.127.116.113027, dated January 25, promoted February 3 – formerly the Maintenance RC viewer.
- RC viewers:
- Project viewers:
- Obsolete platform viewer version 18.104.22.1680847 dated May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.
E-mail Verification Update
The Lab is proceeding with e-mail verification, so again, if you haven’t already done so, please read my post here. There is still no timeline for when the switch-over will occur, and the Lab will provide a blog post as things come into force. Also, while they won’t immediately be affected, this will mean that eventually IMs to e-mail and then marketplace notifications for merchants will ease working for all unverified e-mail addresses.
Links Not Clickable in Group Notices
This is quite an old issue (see BUG-10498), but is apparently occurring again. Speaking at the Server Beta User Group meeting, Mazidox Linden requested if anyone encounters it and can reproduce it, could they please raise a new bug report, stating how they encountered and reproduced the issue.