Release stages
Last updated
Last updated
Release stages make it easy for your team to easily follow a feature's rollout progress.
They reflect the common use case of taking a feature from development to internal testing to an optional beta testing phase, then finally released to everyone.
A release stage consists of a name, color, set of targeting rules, and rollout percentage.
To apply a stage to a feature, go to the Targeting tab and select a release stage that best reflects the feature's current rollout state.
Release stages act as signals of the progression of a feature release to your team.
You can also configure default targeting rules for each release stage that will be automatically applied when you change the stage. You have complete flexibility to add custom release stage targeting rules.
New apps come with 4 default release stages: In development, Internal, Beta, and General availability.
The default release stages come with the following default targeting rules:
Everyone
Staging
No one
Production
No one
Everyone
Staging
Everyone
Production
email contains "@yourcompanydomain.com"
If you don't have a domain set for your organization (for example, you are using a @gmail.com email address), the "Internal" and "Beta" stages won't contain any default targeting rules in the Production environment.
Everyone
Staging
Everyone
Production
email contains "@yourcompanydomain.com"
Everyone
Staging
Everyone
Production
Everyone
You can easily configure targeting rules for release stages, add new stages, or delete existing stages in the App Settings.
You can add or delete release stages based on your rollout process. However, you always need to have at least one release stage.
You can update each release stage's targeting rules to include No one, Everyone, or only specific segments, companies, or users.
If you modify a release stage’s targeting rules, the updated rules are only applied to future features in that stage. Existing features in the stage will retain their existing targeting rules.
