Software Release Glossary

Most commonly used terms and acronyms by product managers, engineers and devops, regarding deployment strategies
BCDFKPRSTV

B

Blue-Green Deployment

Blue-green deployment is a strategy that uses two production environments where traffic is directed to one of these environments once changes are ready.

Read description

C

Canary Deployment

Canary deployment, or canary release, is a deployment strategy that reduces risk by releasing software for testing on a small subset of users.

Read description
CI/CD Pipeline

A CI/CD pipeline is a series of steps which automates the software delivery process allowing releases to be delivered rapidly and efficiently.

Read description
Continuous Delivery

Continuous Delivery is a software development practice that enables code changes to be released to end-users at any time.

Read description
Continuous Deployment

Continuous deployment is a strategy of software release where every change is released to production automatically without human intervention.

Read description
Continuous Integration

A software development practice where developers continuously integrate their changes into the trunk resulting in more stable product releases.

Read description

D

Dark Launch

Dark launch is a software release technique that involves turning on features for a subset of users using feature flags to gather feedback and improve releases.

Read description
DevOps Engineer

A DevOps engineer is an IT professional who oversees the release of new code and facilitates collaboration between development and operation teams for increased productivity.

Read description

F

Feature Branch

Feature branching allows developers to collaborate effectively around a central mainline by keeping any changes to a feature in a separate branch.

Read description
Feature Flags

Software development tool whose purpose is to turn certain functionalities on and off in order to safely test new features without changing code.

Read description
Feature Testing

Feature testing is a software development process that allows you to test several variations of a feature to validate new releases and to determine the one with the best positive impact.

Read description
Feature Toggle

Feature toggles, also known as feature flags, is a technique that allows specific features to be switched on or off quickly and safely for testing purposes.

Read description

K

Kill Switch

A kill switch is a button used to disable features, such as turning off a faulty feature during production, usually implemented through a feature flag.

Read description

P

Progressive Delivery

Progressive delivery is a software development technique where features are gradually rolled out to users to minimize risk of testing in production.

Read description

R

Release Manager

A Release Manager manages all aspects of the software delivery lifecycle and works across teams to ensure a proper release schedule.

Read description
Remote Config

Remote config is a mobile app development technique where the behavior or features of an app can be changed remotely without releasing an app update.

Read description
Ring Deployment

Ring deployment is a technique to gradually introduce new features to different groups of users to limit impact or blast radius on end-users.

Read description

S

Server-Side Testing

Server-side testing refers to any type of testing that occur directly on the web server instead of in the user’s browser.

Read description
Site Reliability Engineer

A site reliability engineer is typically a software engineer with IT operations experience that creates highly reliable systems to solve complex problems.

Read description
Smoke Testing

Smoke testing is a rapid regression test of major functionality to detect early errors and indicate whether the product is ready for further testing.

Read description
Software Development Life Cycle

Software development life cycle (SDLC) refers to the different stages that a software goes through from planning to completion.

Read description

T

Trunk-based Development

Trunk-based development is a practice in which developers divide their work into small batches and later merge their work into a shared trunk or mainline at least once daily.

Read description

V

Version Control

Version control, or source control, is the practice of managing and tracking changes to software code.

Read description
crossmenu
Copy link