Update release docs
What does this MR do?
This MR adds some information about the Helm Chart release process. For me it was to understand how (patch) releases are done and what is automated by the release bot
, which made me dig into the process a bit.
These changes document the repositories, pipelines and tasks involved in the release process.
References:
Related issues
None
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion.
Required
-
Merge Request Title and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes - not applicable
-
Documentation created/updated -
Tests added - not applicable
-
Integration tests added to GitLab QA - not applicable
-
Equivalent MR/issue for omnibus-gitlab opened - not applicable
-
Validate potential values for new configuration settings. Formats such as integer 10
, duration10s
, URIscheme://user:passwd@host:port
may require quotation or other special handling when rendered in a template and written to a configuration file.- not applicable
Edited by Clemens Beck