Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

📖 doc: release tasks: improve polish release note doc #7675

Merged
merged 1 commit into from
Dec 1, 2022
Merged

📖 doc: release tasks: improve polish release note doc #7675

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/release/release-tasks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -289,6 +289,8 @@ The goal of this task to make the book for the current release available under e
6. Sort entries within a section alphabetically.
7. Write highlights section based on the initial release notes doc.
8. Add Kubernetes version support section.
9. Modify `Changes since v1.x.y` to `Changes since v1.x`
Copy link
Member Author

@sbueringer sbueringer Dec 1, 2022 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just adding a note seems okay for now. Modifying the release notes tool for this specific use case (.0 release) isn't worth the effort imho

<br>**Note**: The release notes tool includes all merges since the previous release branch was branched of.
4. Iterate until the GA release by generating incremental release notes and modifying the release notes in hackmd accordingly:
```bash
# PREVIOUS_TAG should be the tag from which the previous release notes have been generated, e.g.:
Expand Down