-
-
Notifications
You must be signed in to change notification settings - Fork 9.9k
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
Update CHANGES.md and NEWS.md with changes that have occurred since 3.2 #23998
Update CHANGES.md and NEWS.md with changes that have occurred since 3.2 #23998
Conversation
Approved but I recommend the following addition. I forgot to mention SSL_poll in CHANGES.md. Neil's RCU work also warrants acknowledgement.
|
* Various optimizations for cryptographic routines using RISC-V vector crypto | ||
extensions | ||
|
||
* Added assembly implementation for md5 on loongarch64 |
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.
Not sure why any of those are mentioned in this section.
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 saw them as "potentially significant" changes, i.e. they're not new features, but things things that people might be interested in anyway.
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.
Maybe we should split this up in more sections? But I'm fine with having that fixed after the release.
I agree this does warrant acknowledgement - but I'm wondering whether doing it in this release is premature since we're not actually really using it yet - its just purely internal changes that no one will notice. Would it be better to defer pulling this into CHANGES/NEWS until such time that we are making substantial use of it? |
Fixup pushed adding the SSL_poll feature to both CHANGES/NEWS. I've not added RCU at this time. |
@hlandau do you agree this is urgent? |
agree urgent |
I have no objection to this going in immediately as I see it as part of the release process... IMO a different kind of authorization than our urgent process. |
Pushed to the 3.3 branch. Thanks for all your input. |
Release: yes Reviewed-by: Hugo Landau <hlandau@openssl.org> Reviewed-by: Neil Horman <nhorman@openssl.org> (Merged from #23998)
Release: yes
I've added the "Release: yes" header for this commit. As per the committer policy the author counts as a reviewer for CHANGES/NEWS updates for a release.
Added the urgent tag as this is needed for today's beta release.
For CHANGES.md I've gone through the commit log for all changes since 3.2 and added several items that I thought justified a CHANGES.md entry but hadn't previously been included.
I've used the new NEWS.md structure as we did for 3.2, but i reordered it so that new features comes first, followed by "significant or incompatible updates". I dropped the sections for known issues and documentation enhancements since I didn't have anything to report there.