How do you as a current service provider deal with the continual lack of Thirdlane Connect backwards compatibility?
This latest release by Thirdlane (based on the release notes) has corrected many of the issues that we have had with Thirdlane and we are considering moving back to the Thirdlane platform and offering PBX as a service again. However, as of right now, we have 3 small clients that remained on thirdlane that we deployed single tenant VMs for with free licenses and 2 of the 3 tenants were complaining on Tuesday morning that they could no longer use Thirdlane Connect because it autoupdated on their mobile devices.
With a release with so many major changes, our normal internal control processes would be to evaluate the release on a separate system to ensure they were no issues before pushing it into a production environment with a 1000 extensions relying on your service to work reliably and stably. Further, we would typically want to give our customers a 2 week notice of a scheduled upgrade process so they are prepared. However, with the lack of backwards compatibility, this approach is virtually impossible.
Do you just yum update and pray the moment you find out a Thirdlane release has been made? How do you handle customer communication? Do you explain to customers that their Connect may not work for a couple weeks while you test the latest release to ensure stability (I can't imagine that would go over well)?
This latest release certainly looks promising and provides a path for us back to unifying customers back onto a single multi-tenant platform, however, I am petrified about the update process and the fact that essentially all updates are "breaking" with limited control over preventing those breaks from occurring.