-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Release v0.30.0-rc.0 #4770
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
base: main
Are you sure you want to change the base?
Release v0.30.0-rc.0 #4770
Conversation
|
Yes, that is very reasonable :-) |
Add CHANGELOG entries. Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
b4a571a to
bb9895d
Compare
Adds changes that have been merged after 2025-11-21 into main. The entry Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
siavashs
left a comment
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.
LGTM, thanks
Previously, the titles were left unchanged from the original PR. We now make the following small adjustments: * Prefixes such as `Feat` and `Fix` are omitted, if they are already covered by `[FEATURE]` and `[BUGFIX]`. * Words indicating the area of improvement are spelled lower case. * Colon is followed by an upper case word. Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
|
Thanks for the review, should be fixed now (including some additional changes, which are in line with the feedback). |
|
Want to update the |
Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
|
Not sure if I got the part about the release date, but I gave it a shot. 🙃 |
SuperQ
left a comment
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.
The release date in the RELEASE.md is just a vague target for the release. We can cut things +- a few days. It's all up to the release manager.
| * [ENHANCEMENT] ... | ||
| * [BUGFIX] ... | ||
|
|
||
| ## 0.30.0-rc.0 / 2025-12-10 |
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.
You set the VERSION to 0.30.0, do you intend to just cut a release or do you want to cut an RC first?
| ## 0.30.0-rc.0 / 2025-12-10 | |
| ## 0.30.0 / 2025-12-10 |
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 would like to a rc first and have adjusted VERSION accordingly.
Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
|
I guess I'll try an expose my thought process a little bit here: I have some changes I'm holding off on, and I imagine others are feeling similarly. That is why I would create a new release branch as soon as possible. Then we can wait a bit to see if there are any bug reports. It would also be nice to have a more complex test environment, but I currently don't have one. Maybe somebody will volunteer their environment. |
Adds CHANGELOG entries.
For convenience, here the same list with the merge date and the author:
For now, is just fixed the capitalization and the markdown syntax in the titles. Feel free to suggest changes. Some entries may be replaced, depending on which requests we merge. I also have a complete list of the PRs I reviewed, and why they did not make into the changelog.
EDIT: Newly added entries below.