Release notes on elemental.docs.rancher.com #165
Assignees
Labels
Comments
|
Assigning to @nunix asking for respective docs infrastructure/setup so that engineering has a place to put release notes. We need (at least) three components
Each component is versioned. Release notes are per-component, per-version. |
nunix
added a commit
to nunix/elemental-docs-repo
that referenced
this issue
Jul 28, 2023
The release notes page has been added to `v1.2` and `next` versions. The page will be part of the docs versioning and the versions listed in the release notes are fixed to the specific version. This PR addresses rancher#124 rancher#165 and rancher#176 Signed-off-by: Nuno do Carmo [email protected]
nunix
added a commit
that referenced
this issue
Jul 30, 2023
* Added release notes page The release notes page has been added to `v1.2` and `next` versions. The page will be part of the docs versioning and the versions listed in the release notes are fixed to the specific version. This PR addresses #124 #165 and #176 Signed-off-by: Nuno do Carmo [email protected] * Applied @fgiudici feedback Signed-off-by: Nuno do Carmo [email protected] * Updated v1.2 with @fgiudici feedback Signed-off-by: Nuno do Carmo [email protected] --------- Signed-off-by: Nuno do Carmo [email protected]
|
Release notes page has been implemented. This issue can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(This is a possible solution/workaround for rancher/elemental#875)
As we release new versions (of elemental, elemental-operator, or the node image), we need a way to inform users
about the changes within.
Esp. the backup/restore fix needs manual intervention to take full effect.
We should start by enhancing our documentation with "release notes" for the various components.
Long-term, these release notes should be visible in the UI though.
The text was updated successfully, but these errors were encountered: