A release is a version of the product intended for use outside the development team. A release need not be customer-centric. Some teams differentiate between internal release (e.g. for QA or demo activities) and external release (e.g. for customers or production).
Ideally, a release is associated with a checkpoint in the version control system and generated through a well-defined, repeatable process. ("We are preparing the 1.2.0 release now."). Releases can be classified as major, minor or patch releases where the version numbering sequence is defined by three-digit sequence identifying Major.Minor.Patch
Each release is described in a release plan. The release plan is a tactical document designed to capture and track the features planned for an upcoming release. The release plan communicates those features and enhancements planned for the product’s release. It acts a mini-project plan, breaking the big ideas of the product roadmap down into smaller steps the team can make progress on.
The portfolio level governance can decide to only relate to major or minor releases.
The portfolio level governance can decide to only relate to major or minor releases.
