Product release phases

Learn the about the performance and support expectations for “experimental”, “preview”, “beta”, and “GA” release phases.

In the Labelbox platform, you may see that some features are marked as “experimental,” “preview,” or “beta.”

Each serves a distinct purpose in our product development cycle.

Each phase comes with its own set of support and performance expectations.

This guide defines each phase and the level of support you can expect.

Experimental

  • Definition: Experimental features are still being tested and validated by our team. Experimental features are made available to select customers in order to solicit early feedback. These are very early-stage features that may be removed or altered at any time.
  • Support Expectations: No official support is provided during this phase. Users who choose to participate in experimental releases may encounter bugs, glitches, or an incomplete experience. The feature may be removed from the platform at any time, without warning.
  • Performance Expectations: Performance may vary significantly as our team is actively refining the feature based on user feedback.

Preview

  • Definition: Preview features in the preview phase are likely to be more stable than experimental features, but they are still undergoing testing and validation. This phase is typically reserved for early features in order to get feedback from a slightly larger group of customers.
  • Support Expectations: Limited to no official support is provided during this phase unless specified by our team. Not all features may be fully functional or polished. The feature may be removed from the platform at any time, with no warning.
  • Performance Expectations: Performance may vary, and users may encounter bugs or inconsistencies.

Beta

  • Definition: Beta features are nearly complete. Beta features are released to a wider audience for real-world testing.
  • Support Expectations: Limited support is typically available during beta. Users are encouraged to report any issues they encounter during this phase.
  • Performance Expectations: The feature should be fairly stable and functional. However, minor bugs or performance issues may still exist.

General Availability (GA)

  • Definition: General availability marks the official public release of the feature or product. It is considered fully developed and ready for widespread use.
  • Support Expectations: Full support should be available.
  • Performance Expectations: The feature should offer optimal performance with minimal bugs or issues. Future updates and patches will address any unforeseen issues.