For major projects developed with customer input, we use a three-step release process to manage risks and improve product quality:
Closed Beta is a phase in our development process when we invite a select group of users to try out a new feature or product before it's launched to the public. This allows us to test performance, gather user insights, and fix potential bugs before a broader release.
Important points to keep in mind during the Closed Beta phase:
- Expect bugs: Since it's a testing phase, you may encounter issues.
- Compatibility: The Closed Beta version may not be compatible with all systems or previous versions.
- Incomplete Features: Features in this phase may not be complete or fully functional yet.
- Performance: The beta version may not yet be optimized for performance and scalability.
- Release Uncertainty: Not all features tested in Closed Beta are guaranteed to be released.
Please note, your feedback during this phase is crucial in shaping the final product.
Open Beta is a phase when all customers are welcome to test a new feature or product. Unlike Closed Beta, Open Beta isn't limited to specific testers - anyone can join in.
The goal of Open Beta is to gather feedback from a large user base to pinpoint and address any missed bugs, issues, or usability problems. This feedback aids in refining the product before its general release.
Remember, Open Beta is still a developmental stage, meaning you might encounter bugs or performance issues. Your feedback and problem reports are crucial for improving the product.
- Minor issues may occur.
- There may be compatibility issues.
- Features may still be incomplete.
- Only main localization (US English) is supported.
- The product may not be fully optimized for wider release.
Our Help Center documentation is updated prior to any Open Beta release.
General Release is the final development stage when a new feature or product is stable, fully functional, and complete. By this point, all major bugs have been resolved, and end-user documentation and full translation are finalized.
This stage marks the end of the development cycle and begins the product's lifecycle, which may include updates, fixes, or new features.
Before making a feature generally available, we ensure usability and value risks are addressed. This is important for users to recognize its value and for us to measure adoption after it is released to everyone.
How do the release stages differ?
|Yes, but with caveats and limitations
|By invitation only
|Service desk ticket
|Service desk ticket
|Test only / Test or production
|Test and/or production
|Service desk and Service Level Agreement (SLA)
|Best effort and no SLA
|Full Service Desk and defined SLAs
|Draft. Accessible to Closed Beta customers only.
|Draft is publicly available, but may be incomplete
|Public and complete
|“Best effort” basis leveraging help documentation.