2018 SL UG updates 51/3: TPV Developer meeting summary

Dagger Bay; Inara Pey, November 2018, on FlickrDagger Bayblog post

The following notes are taken from the TPV Developer meeting held on Friday, November 30th, 2018. A video of the meeting is embedded below, my thanks as always to North for recording and providing it. Note that was a brief meeting, with extended silences while things were discussed in chat.

SL Viewer

[0:53-4:05] The Love Me Render RC viewer updated to version, dated December 18th.

  • Current Release version, dated December 5, promoted December 13. Formerly the Spotykach Maintenance RC viewer – NEW.
  • Release channel cohorts:
    • Estate Access Management (EAM) RC viewer, version, December 19.
    • BugSplat RC viewer, version, December 18. 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. It also makes the version update check a child process to the viewer, which should prevent the creation of multiple viewer icons.
  • Project viewers:
  • Linux Spur viewer, version, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
  • Obsolete platform viewer, version, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.

Currently, it would appear that the BugSplat RC will most likely be the next RC viewer promoted to release status.

As per my most recent CCUG summary, the Bakes on Mesh viewer will most likely have one more round as a project viewer before moving to RC status. It is also hoped that the EEP viewer will go to RC status in early January.

Feedback from estate / region owners / managers is still being sought for the Estate Access Management viewer, so if you have estate / region management rights for a region / estate, please give the viewer a go and report any issues back to the Lab via Jira.

Voice Service Update

[5:08-6:02] The Lab is planning an update to the voice service back-end over the holiday period. This should have been deployed prior to the break, but had to be postponed. When deployed, it could cause a brief interruption to services, and users may have to re-log to regain voice. Notification of the deployment will be given ahead of time via the grid status page. There is also a roll-back plan in place if the update causes issues.