Release
A release is a planned version or set of changes prepared for delivery to users or a target environment.
It usually represents the business or product view of a change set, while deployment is the operational act of putting it into an environment.
What it does
A release packages work into a deliverable version.
It is commonly used to:
- Group features, fixes, and changes together
- Mark a version as ready for rollout
- Communicate what changed
- Coordinate testing and approval
- Prepare for deployment into staging or production
Core concepts
Versioned change set
A release usually represents a specific build, version, or approved set of changes.
Release vs deployment
A release is the planned deliverable.
A deployment is the action of applying that deliverable to an environment.
Business and technical alignment
Releases often matter to both technical teams and stakeholders because they connect implementation work to actual shipped outcomes.
Common use cases
- Feature launches
- Bug-fix rollups
- Scheduled maintenance windows
- Versioned software delivery
- Coordinated updates across environments
Practical notes
- A release can exist before it is deployed.
- Some teams release frequently in small batches, while others bundle larger sets of changes together.
- A good release process usually includes QA, staging review, deployment planning, and rollback readiness.
- In WordPress workflows, a release might include code, plugins, themes, configuration, or content changes.
Frequently Asked Questions
Is release the same as deployment?
No. A release is the version or planned change set. Deployment is the action of applying it to an environment.
Does every release go straight to production?
No. Releases are often validated in staging or QA before reaching production.
Why separate release from deployment?
Because it helps teams plan, test, approve, and communicate changes before they go live.