Release Process
Overview
Continuous Deployment does not require big up front design.
Larger features benefit from planning focusing on how to test and release the feature.
A feature is made up of many deploys.
Every deploy is a production-ready step to the complete feature.
There is no manual QA in the deploy pipeline.
Instead, manual QA is a part of the feature release process.
Continuous Deployment does not mean releasing half-baked features.
We conditionally enable code paths to control exactly when and how the feature is released.
Larger features benefit from planning focusing on how to test and release the feature.
A feature is made up of many deploys.
Every deploy is a production-ready step to the complete feature.
There is no manual QA in the deploy pipeline.
Instead, manual QA is a part of the feature release process.
Continuous Deployment does not mean releasing half-baked features.
We conditionally enable code paths to control exactly when and how the feature is released.
Continuous Deployment gives you the power
to choose exactly what and when to release.
to choose exactly what and when to release.
(Reading...)
Formatting Hints:
To format... | use this markup: |
---|---|
source code | {source:lang=java|lineNumbers=false}...{source} (Supported languages: java, cpp, csharp, c, python.) |
bold text | __some text__ |
italicized text | ~~some text~~ |
underlined text | @@some text@@ |
a method or class name | ``myMethod(...)`` |