Skip to content

Commit

Permalink
Update patterns/2-structured/release-process.md
Browse files Browse the repository at this point in the history
Co-authored-by: Sebastian Spier <[email protected]>
  • Loading branch information
dgrizzanti and spier authored Aug 8, 2023
1 parent c7abae2 commit 5abbd99
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions patterns/2-structured/release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,9 @@ In addition to building your source code, writing release notes can be tedious w
If a company does not provide a centralized location for storing build artifacts (jars, npm modules, etc.) and docker images, engineers may be left deciding for themselves where is appropriate to store versioned software. Tools like GitHub provide this for you, however, if a company is not using one of these popular tools, this could pose a burden.

## Solution

Check failure on line 39 in patterns/2-structured/release-process.md

View workflow job for this annotation

GitHub Actions / lint

Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "## Solution"]
By providing clear **release notes** and a published artifact you increase people's confidence that you are publishing a quality product that they can rely on.

The following are key elements to achieve this:

- CI/Delivery Pipeline is located within your repo to build artifacts (binary, docker image, jar, etc)
- Releases and accompanying build artifacts are generated by the CI system
Expand Down

0 comments on commit 5abbd99

Please sign in to comment.