forked from google/boringssl
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Review project status #108
Comments
I agree. Here is the current plan
|
There's been a liboqs release, so where do we put a new Chromium build (and for which platforms)? |
Yes I noticed that. We're on the spring festival holiday now; we will build one in early March. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In checking all OQS subproject statuses we've also come across this project: It doesn't seem overly active (e.g., actively following the upstream master), so we wonder whether this should somehow be reflected in the README. @pi-314159 any suggestions in this regard?
The text was updated successfully, but these errors were encountered: