-
Notifications
You must be signed in to change notification settings - Fork 69
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.
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
Release Notes v1.73.0 #694
Conversation
content/en/news/release-notes.md
Outdated
@@ -6,6 +6,33 @@ weight: 1 | |||
|
|||
For additional information check our [sprint demo videos](https://www.youtube.com/channel/UCcm2NzDN_UCZKk2yYmOpc5w) and [blogs](https://medium.com/kialiproject). | |||
|
|||
## v1.73.0 | |||
Sprint Release: Sep 15, 2023 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We released 1.73 on August 28.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh! That's a wrong date - It is supposed to be for 1.73.
The release notes from 1.73 are missing, right? (That's why I created this PR)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused about this PR - it says "1.73" with a date in the future of Sept 15, and it has issues that were just merged. Is this for 1.74? If so, we are missing 1.73 release notes. If this is for 1.73 then the notes have been generated with the wrong issues and the date should change from Sept 15 to Aug 28 in the release-notes.md
I used the relnotes.py script, not sure if it could be used for 1.73 (As it uses the project number but we are reusing it now) |
@jshaughn knows the magic in that relnotes script - he can tell you how to generate for an already-released kiali |
Hmmm, I didn't notice that we didn't gen release notes for 1.73. The issue here, well, at least one issue, is that we archived the "Done" column in the project board. The release notes really need to be generated after everything is moved to Done and before archiving and then repopulating Done with stuff from the next sprint. Let me see what I can do... |
Maybe we could use a filter by dates in such case? (In the UI I used |
this PR can be closed - the release notes were done in these PRs: |
Release notest for 1.73