release
/rɪˈliːs/noun
A release is an identifiable software version prepared to be made available to users. It brings together one or more checked changes.
After the final checks, we will make the release available on Thursday evening.
A release brings together software changes ready for use. It may be a major new version, a small adjustment or a security update. The team decides which changes belong in it and usually identifies the version with a number, label or date.
What belongs in a release?
Before making a release available, the team checks that its features and fixes work properly. This can involve automated tests, an acceptance environment and Glossary · In briefregression testA regression test checks that previously working parts of software still behave as expected after a change, revealing unintended effects.Read more. A Glossary · In briefchangelogA changelog is a record of relevant software changes, usually organized by version or release. It includes new features, bug fixes and changes that affect users.Read more can record what changed and which known limitations remain.
Not every release reaches all users immediately. A team can use a version internally first, offer it to a test group or gradually enable it with a Glossary · In brieffeature flagA feature flag is a setting that enables or disables software functionality without another code deployment. It can apply to all users or a particular group.Read more. The release remains identifiable while availability differs between groups.
Release and deployment
A release and a Glossary · In briefdeploymentA deployment is the process of installing and starting a chosen software version in a target environment so it can be tested or used there.Read more are closely related but different. The release is the software version you intend to make available. Deployment is the technical process of installing or activating it in an environment.
Sometimes they coincide: deploying to production makes the release visible immediately. For mobile apps, software may already have been submitted to an app store while users receive the update later. A deployment can also happen without a new release, for example when reinstalling the same version on a recovered server.