jimeh/common-flow
1
0
Fork 0
mirror of https://github.com/jimeh/common-flow.git synced 2026-02-19 09:26:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

Pre-release releases are not safe for production use

Browse Source
This commit is contained in:
Jim Myhrberg
2017-07-10 21:13:01 +01:00
parent 7ed4cdf687
commit 40bfd924d4
1 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
common-flow.md
View File

@@ -29,9 +29,9 @@ Terminology
branch. branch.
- **Pull Request** - A means of requesting that a change branch is merged in to - **Pull Request** - A means of requesting that a change branch is merged in to
its merge target, allowing others to review, discuss and approve the changes. its merge target, allowing others to review, discuss and approve the changes.
- **Release** - Is considered safe to use in production environments. Consists - **Release** - May be considered safe to use in production
of a version bump commit, and a git tag named according to the new version environments. Consists of a version bump commit, and a git tag named according
string placed on said commit. to the new version string placed on said commit.
- **Release Branches** - Used both for short-term preparations of a release, and - **Release Branches** - Used both for short-term preparations of a release, and
also for long-term maintenance of older version. also for long-term maintenance of older version.
@@ -52,8 +52,7 @@ interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119).
suite passing. suite passing.
4. The master branch IS NOT guaranteed to always work in production 4. The master branch IS NOT guaranteed to always work in production
environments. Despite test suites passing it may at times contain environments. Despite test suites passing it may at times contain
unfinished work. Only releases must be considered safe for production unfinished work. Only releases may be considered safe for production use.
use.
5. The master branch SHOULD always be in a "as near as possibly ready for 5. The master branch SHOULD always be in a "as near as possibly ready for
release/production" state to reduce any friction with creating a new release/production" state to reduce any friction with creating a new
release. release.