Meta Release Process

What is a Meta release?

Meta releases are preliminary releases of the core VMS software (like alpha or beta versions). Those builds are created specifically for developers and partners to create integrations with the software before the official release.

How often do we make Meta releases?

There is no pre-defined schedule for Meta releases. We make a decision to roll out a new version primarily based on two considerations:

1. Are there any specific support tickets that we need to address?
2. Do we have enough changes which affect partners and require them to update their code base?

Once we decide to make a release, it contains all the changes accumulated up until that point. It is possible to influence a Meta release by creating a support ticket or a discussion on the Developer forum and explain your issue or proposition. All requests are considered, and if possible, addressed in upcoming Meta releases. 

Are Meta releases stable?

No. A Meta release cannot be considered stable by any means, because it always contains untested changes in the core of the software. Every time we release a Meta, we test and try to stabilize only the most essential features, allowing our partners to continue their development.

That being said – you should always use the latest build, because every version introduces new capabilities for developers or some changes in the SDK. Check release notes to see the specific list of important changes

What do we test before a new Meta release?

Before a new Meta release is launched, we perform two tests (commonly called a "smoke check"):

• Core software features, including live streams, archive playback, setting dialogs, web admin interface, and Cloud connectivity.
• Development-related features, including stub plugin with events, objects and settings, SDK compiling, searching through the analytics database, and documentation changes.

The tests are performed on three platforms: Windows, Ubuntu x64, and ARM64.

Each new Meta release is bundled with Release Notes. This document contains a comprehensive list of changes, bug fixes, and known issues. If a known issue from the previous release is fixed, we list it as a Fixed Issue in the current release.

If a Meta release contains some important new features, fixes for support tickets, etc., those features and fixes are tested immediately before or during the smoke check.

Is it expected that the new Meta release might break plugin compatibility with the VMS?

Yes. Moreover, 3rd-party developers have to change their code accordingly because the primary goal for a plugin is to be compatible with the upcoming major VMS release.