Uptempo's Feature Release Lifecycle

Introduction

The feature release lifecycle is the process that we use for adding new features to Uptempo's Plan, Spend, and Work products, and for removing features when they reach the end of their lifespan. It covers:

  • How we make new features available to Uptempo customers

  • How we communicate changes in a feature's status during each stage of the lifecycle.

The Uptempo product lifecycle consists of three release stages for new features, and two deprecation stages for retiring features. This page describes these stages, and what you can expect at each stage.

Release Stages

Overview

We release new features to the Uptempo platform in three stages:

Order Release Stage Definition Availability
Stage 0 Beta New incomplete features that are still being actively developed based on customer feedback.
Available to selected customers by invitation.
Stage 1 Preview New complete features that are ready to use, but are not yet turned on automatically for all customers.
Available to all customers who opt in.
Stage 2 General Availability New complete features that are ready to use, and are turned on automatically for all customers. Available to all customers automatically.
  • All major new Uptempo Plan and Uptempo Spend features are released into the Preview stage first.

    • For technical reasons, all Uptempo Work features are released directly into the General Availability stage.

  • After two monthly release cycles, features in the Preview stage are automatically transitioned into the General Availability stage.

  • All minor new features bypass the Preview stage, and are released directly into the General Availability stage.

  • Only certain new features are released into the Beta stage. When a Beta feature is ready for a wider rollout, it transitions to the Preview stage, and finally to the General Availability stage as usual.

Note

Bug fixes are not part of this process, and are always released directly into the General Availability stage.

Stage 0: Beta

What: We release some new features into the Beta stage first. Features in this stage are still being actively developed and may be missing certain functionality, so they are not yet widely available.

Who: We offer Beta features to selected customers, who work with us to provide valuable feedback from real-world usage.

Why: The purpose of the Beta stage is to make sure that we're building features that meet all of our users' needs. Throughout the Beta stage, we use tester feedback to continuously evolve and improve features and make them ready for wider release.

When: The Beta stage does not have a fixed length. A feature may be in this stage for just one monthly release cycle, or for multiple release cycles, depending on user feedback. When features exit the Beta stage, they usually move into the Preview stage next.

Note

The Beta stage was previously called Early Access.

Stage 1: Preview

What: We release major new features into the Preview stage. Not all new features are released into this stage: minor enhancements, such as UX/UI and performance improvements, bypass this stage and are released directly into the General Availability stage.

Who: Features in this stage are available to all customers, but require manual activation before they can be used.

Note

For new customers who are still in the onboarding phase, features that are released into the Preview stage are turned on automatically.

Why: The purpose of this stage is to minimize disruption to our customers. The Preview stage lets you choose exactly when you want to begin using a major new Uptempo feature, and gives you time to plan and prepare to roll it out in your Uptempo environment.

When: The Preview stage has a fixed length. Features released into this stage remain in Preview for two monthly release cycles, after which they are automatically transitioned to the General Availability stage.

Stage 2: General Availability

What: Features in this stage are automatically turned on in all customer environments. Major features that were previously in the Preview stage are automatically transitioned into the General Availability (GA) stage after two monthly release cycles. We also release minor enhancements into this stage directly.

Who: Features in this stage are available to all customers, and do not require any action before you can use them.

Why: The purpose of this stage is to make new features available to our entire customer base by default.

When: The GA stage does not have a fixed length. If we need to retire a feature from the Uptempo platform, we transition it to the Deprecation stage. See the section Deprecation Stages for more information about how we retire features.

Deprecation Stages

Overview

From time to time, we must remove features from the Uptempo platform for various reasons. To give customers time to prepare and adjust, we retire features in two stages:

Order Deprecation Stage Definition Availability
Stage 1 Deprecation Features that are still available in the Uptempo platform, but are planned to be removed with a future release. Available only to existing users; not available to new users.
Stage 2 Discontinuation Features that have been removed from the Uptempo platform. Not available to any user.
  • Most retiring features enter the Deprecation stage first. This stage acts as the official announcement that we plan to remove this feature from the Uptempo platform.

  • After the deprecation period (which varies based on the feature), the feature is eventually moved to the Discontinuation stage. Entering this stage means the feature has been removed from the Uptempo platform, and can no longer be used in any form.

  • In very rare cases, features bypass the Deprecation stage and enter the Discontinuation stage directly. We generally do this only for features that are not being actively used by any customer, or in exceptional cases where it is not possible to provide a deprecation period.

Stage 1: Deprecation

What: When we decide to remove a feature from the Uptempo platform, we announce this by moving the feature into the Deprecation stage. In this stage the feature is still available in the product, but is planned to be removed at a future date. Very rarely, some features may bypass this stage and enter the Discontinuation stage directly.

Who: Features in the Deprecation stage only remain available to existing users (customers who previously had access to the feature). Deprecated features are not made available to customers who were onboarded after the feature entered this stage.

Why: The purpose of this stage is to notify current users that we are planning to retire a feature. The Deprecation stage gives you time to transition away from using the feature, and move to an alternative (if applicable).

When: The length of the Deprecation stage is variable, and depends on factors like the size of the feature, the number of affected customers, and the complexity of moving to an alternative. In all cases, we work with affected customers to ensure that they have enough time to adjust to the removal of a feature.

Stage 2: Discontinuation

What: Features in the Deprecation stage eventually move into the Discontinuation stage at the end of the deprecation period. In this stage, the feature is completely removed from the product. In rare cases, features that have no active users, or that have to be removed immediately for technical reasons, are discontinued immediately.

Who: Discontinued features are no longer available to any Uptempo user.

Why: The purpose of this stage is to remove functionality from the Uptempo platform, generally for business or technical reasons.

When: Discontinued features are removed from the Uptempo platform permanently (although in some cases, discontinued features may be replaced by newer alternatives).