daily-email: add 2023-06-21
Deployments vs releases
This commit is contained in:
parent
3650dc65a9
commit
32085ad732
1 changed files with 18 additions and 0 deletions
18
src/content/daily-email/2023-06-21.md
Normal file
18
src/content/daily-email/2023-06-21.md
Normal file
|
@ -0,0 +1,18 @@
|
||||||
|
---
|
||||||
|
title: >
|
||||||
|
Deployments or releases
|
||||||
|
pubDate: 2023-06-21
|
||||||
|
permalink: >
|
||||||
|
archive/2023/06/21/deployments-or-releases
|
||||||
|
tags:
|
||||||
|
- deployments
|
||||||
|
- releases
|
||||||
|
---
|
||||||
|
|
||||||
|
"Deployments" and "releases" are often used interchangeably but mean different things.
|
||||||
|
|
||||||
|
A deployment moves a change from one place to another, such as some updated code from a staging environment to production.
|
||||||
|
|
||||||
|
A release is when the change made is available to users.
|
||||||
|
|
||||||
|
They can happen at the same time, or you can use feature flags to separate them, deploying the code in advance, and the change is only released (or unreleased) by toggling the feature flag.
|
Loading…
Add table
Add a link
Reference in a new issue