-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Upstream release process
-
In Progress
-
False
-
-
None
-
None
-
None
Goal:
To implement the goals described in https://community.theforeman.org/t/rfc-the-perfect-release-process/ in the repositories that are included in Satellite.
Foreman plugins can look at foreman_plugin_template for a best practice: RELEASE.md and .github/workflows/release.yml.
Acceptance Criteria:
Copied from the RFC:
- A project MUST document its release process
- The release documentation SHOULD be in the repository itself using RELEASE.md
- The release documentation SHOULD NOT be in the released artifact.
- A project SHOULD publish artifacts using GitHub Actions
- If the project publishes artifacts using GitHub Actions, the workflow file MUST be called .github/workflows/release.yml
- A project MAY implement a single-command release process so developers can run make release VERSION=x.y.z
To make it easier for projects, the Foreman project as a whole MUST provide a list of recommended GitHub Actions to publish artifacts.
MUST/SHOULD/MAY as described in RFC2119.