[BUILD-527] Implement a release process for magnolia-mgmt Created: 07/Sep/21 Updated: 27/Oct/22 |
|
| Status: | Open |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Epic Link: | Release automation |
| Team: |
| Description |
|
By now the project is deployed to ECR (Docker image artifacts) & AWS (production deployment), so technically there is no need for releases. Still, it would be nice to document what goes from one version to the next. And that we get in the habit of updating the CL before we bump the version. For that we can probably copy-paste the following example: https://git.magnolia-cms.com/projects/BUILD/repos/poms/browse/CHANGELOG.adoc?useDefaultHandler=true |