-
Notifications
You must be signed in to change notification settings - Fork 654
liboqs 0.15.0 release candidate 2 #2317
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
Conversation
Signed-off-by: Ganyu (Bruce) Xu <[email protected]>
|
If we push back a release because of a fix to a bug reported in April, I'd then argue we should also include in 0.15.0 an improvement from this month (#2312) easing the (integration) life of users. PR is ready to merge but I'd leave it to you @xuganyu96 to merge and include or not. |
I want to push back against including #2312. "...push back a release because of a fix to a bug reported in April" was not my intention. Some miscommunication caused #2310 to land before I could remove the "release candidate 1" tags and do the full 0.15.0 release. Perhaps in the next status call we could briefly discuss how to do some kind of "merge freeze" between release candidate and full release. |
OQS release test |
My motivation for seeing this included is that it fixes a bug in terms of which algorithms are available in the build configuration -- and availability of algorithms is kind of a "top-level" line item feature. |
|
@baentsch I need one more approval to merge this pull request. Thank you. |
|
@xuganyu96 you got it from @ashman-p : As this is LMS-related, his approval is the relevant one. |
liboqsrelease candidate 2Because #2310 changed the list of LMS variants under the build flag
OQS_ENABLE_SIG_STFL_LMS, a second release candidate is necessary. The target release day is Monday, Nov 10.