Releases Glossary

Browse 72 releases terms defined in plain English, from the cultural dictionary of computing.

72 Releases Terms

Alpha
A very early version of software released for limited testing or internal use before the product is considered feature-complete or stable. In slang usage,...
Application Version
The specific release identifier of an application build, used to distinguish deployed code, track changes, and correlate behavior with a known state of the...
Beta
A pre-release stage where software is more complete than alpha but still being tested by selected users or the public before full release. In casual tech...
Bumping Version
Informal shorthand for increasing a version number, usually during a release or dependency update. In developer slang, 'just bump the version' can make a...
Change Freeze
A period when changes are restricted or paused to reduce risk, usually around major launches, holidays, or critical incidents. In operations culture, a change...
Change Log
A record of changes made over time to a product, codebase, document, or system. In culture and practice, change logs are part documentation, part trust signal,...
Changelog Culture
A team habit of documenting and communicating changes consistently through release notes, internal updates, and visible records. Changelog culture matters...
Changelog Drama
Conflict or backlash triggered by how product or project updates are described in release notes or changelogs.
Code Version
A specific identified state of source code, usually represented by a commit, tag, branch point, or release identifier. Knowing the exact code version is...
Crash and Burn
To fail dramatically, often after a launch, demo, or ambitious technical effort goes badly wrong in a visible way. It implies not just failure but failure with...
Deploy Day
The scheduled day when a team typically pushes releases, often carrying its own rituals, nerves, and pacing. In engineering slang, deploy day can be either a...
Deploy Party
A shared team event around a deployment, sometimes celebratory and sometimes half-joking because everyone needs emotional support. In engineering slang, deploy...
Deploy Window
The time period during which deployments are allowed or considered safe to perform. In engineering slang, deploy windows exist to align with support, staffing,...
End of Support
The point after which a version, product, or distribution no longer receives official fixes, updates, or maintenance. In infrastructure culture, end of support...
Experimental Feature
A feature released in a limited or provisional state to gather feedback, validate demand, or explore technical feasibility before broader commitment. In...
Feature Flag Culture
A team's habits and expectations around using feature flags for rollout control, testing, safety, and experimentation. Healthy feature flag culture includes...
Feature Freeze
A period when no new features are allowed so the team can stabilize, test, and prepare a release candidate. Only fixes and critical changes usually get...
Feature Launch
The process of releasing and introducing a feature to users, customers, or internal teams. In product culture a feature launch includes not just shipping code...
Feature Preview
An early look at a feature before full release, often shared with selected users or publicly as a way to gather feedback and build interest. In product culture...
Feature Rollout
The controlled release of a feature to some or all users over time. In product culture feature rollout is where technical safety and user communication meet,...
Feature Toggle Culture
A culture centered on using toggles to separate deployment from release and to manage exposure more flexibly. The phrase is similar to feature flag culture but...
General Availability
The stage at which a product, feature, or service is considered ready for broad production use and official support, often after preview or beta phases. In...
GitHub Release
A tagged release entry on GitHub used to package release notes, binaries, source snapshots, and version milestones in a repository. It is a standard way to...
Lame Duck Release
A release that is technically still supported or publicly available but already overshadowed by its replacement and receiving minimal strategic attention....
Landed
Merged, deployed, or otherwise successfully applied in the target environment. Engineers use it for code changes, features, fixes, and sometimes policy...
Launch
The coordinated release and introduction of a product, feature, or company message to users or the market. In startups, launch usually combines product...
LTS
Short for long-term support, indicating a release expected to receive fixes and maintenance for an extended period. In open-source culture, LTS versions are...
LTS Release
A long-term support release intended to receive bug fixes and security updates for an extended period compared with regular releases. LTS releases are favored...
Major Version
The highest-order number in a versioning scheme, typically used to signal breaking changes or major shifts in compatibility under semantic versioning...
Minor Version
The middle segment in a semantic version number, commonly used to indicate backward-compatible new functionality without breaking existing integrations. Minor...
Model Release
A released version of a model made available for testing or production use. Model releases may include updated weights, changed behavior, new limits, or...
Nightly
Describing builds or releases generated frequently, often every night, from the latest state of development rather than from a stable release branch. In...
One More Fix
The dangerous promise that there is only one small additional change before a release or merge, even though such promises often multiply. Teams hear it most...
Package Publishing
The process of preparing, versioning, signing if needed, and uploading a software package to a registry or repository so others can install it. In mature...
Package Version
The version identifier assigned to a package release. In package ecosystems, package versions are critical for dependency resolution, upgrade behavior,...
Point Release
A small release, usually reflected in the final segment of a version number, intended to deliver bug fixes, minor improvements, or maintenance updates without...
Prerelease
A release published before official stable release, often marked alpha, beta, rc, or preview, to gather testing and feedback. In release culture, prereleases...
Production Ready
Good enough to run for real users under real operational conditions, with acceptable reliability, observability, security, and support characteristics. Teams...
Project Changelog
The changelog associated with a specific project, documenting releases, fixes, breaking changes, and other notable updates. In open-source culture, a readable...
Project Release
A release of a project's software, documentation, or assets, often tied to a version and changelog. In maintenance culture, project releases are moments where...
Ready to Ship
Prepared enough for release, including not just code completion but the surrounding confidence and support work that make shipping responsible. In engineering...
Release Asset
A file attached to a software release, such as a binary, archive, checksum, or installer. In release engineering culture, assets are the concrete deliverables...
Release Automation
The use of scripts, pipelines, and tooling to build, version, test, package, sign, and publish software releases with minimal manual intervention. Strong...
Release Binary
A compiled executable or binary artifact produced for a release and intended for end users or deployment systems. In practical software distribution, release...
Release Branch
A branch reserved for preparing, stabilizing, or maintaining a release line separately from ongoing feature development. In engineering culture, release...
Release Cadence
The rhythm or frequency with which a project publishes new versions, such as weekly, monthly, or on-demand. Release cadence affects user expectations,...
Release Checklist
A documented sequence of tasks required to ship a release, such as verifying tests, updating changelogs, tagging versions, checking signatures, and...
Release Draft
An unpublished or provisional release entry prepared before final publication, often with notes and attached artifacts still under review. In repository...
Release Engineering
The discipline of building, packaging, validating, and shipping software releases in a reliable and repeatable way. In mature engineering organizations,...
Release Notes
Documentation published with a release that explains what changed, what was fixed, what broke, and what users should know before upgrading. Good release notes...
Release Party
A team celebration around shipping a release, sometimes sincere and sometimes half-joking because everyone is too exhausted to call it elegant. In engineering...
Release Pipeline
The automated sequence of steps used to build, test, package, sign, and publish a software release. In DevOps culture, the release pipeline is where trust in...
Release Strategy
The intentional plan for how a project versions, packages, stages, communicates, and rolls out software changes over time. Release strategy includes decisions...
Release Tag
A version tag in version control marking the exact commit associated with a release. In repository practice, release tags make it easy to trace distributed...
Release Version
The version identifier assigned to a particular release of software or an artifact set. In maintenance culture, release versions are the handles people use to...
Rollback Slang
A loose use of 'rollback' for any retreat to an earlier safer state, whether that means undoing code, disabling a feature, or backing out a policy decision. It...
Rolling Release
A release model where software is updated continuously rather than through large, infrequent version jumps. Rolling releases give users faster access to...
Rollout
The staged introduction of a product, feature, pricing change, or program to users or markets. Rollouts can be gradual, segmented, or region-based to manage...
Security Release
A software release whose primary purpose is to deliver one or more security-related fixes. In maintenance culture, security releases are usually communicated...
Shipping Cadence
The rhythm or frequency with which a team releases changes, features, or updates.
Silent Deploy
A deployment designed to minimize external visibility and user disruption, often by releasing infrastructure, code paths, or toggled-off features before public...
Soft Launch
A limited or quiet release to a small audience or low-profile channel before a broader public launch. Teams use it to test real-world behavior without the full...
Stable Branch
A branch maintained for reliable use, usually receiving bug fixes and patches while avoiding risky feature work. In release management, stable branches give...
Stable Release
A version of software intended for reliable use in production, with reduced change velocity and stronger expectations around backward compatibility and...
Unstable Branch
A branch intended for ongoing development where changes land before they are fully tested, frozen, or prepared for wider consumption. It is often contrasted...
Update Channel
A release track through which users receive updates, such as stable, beta, nightly, or security-only. In software distribution, update channels let teams serve...
Version Bump
A change that increments a project’s own version number or updates the version of a dependency it uses. Version bumps can be mechanically simple but...
Versioning
The practice of assigning and managing versions for software, APIs, schemas, or artifacts over time. In engineering culture, versioning is how teams...
Versioning Strategy
The overall approach a project takes to numbering releases and signaling compatibility, stability, or lifecycle stage to users. A versioning strategy may use...
Version Policy
The documented rules a project uses to decide when and how version numbers change, how long versions are supported, and what compatibility promises they imply....
Weekend Deploy
A deployment performed on a weekend, usually because business constraints, maintenance windows, or risky migrations made normal hours undesirable. The term...
Weekly Release
A release process or policy where a project publishes updates once per week, creating a predictable rhythm for packaging, review, and user expectations. Weekly...

Related Topics