-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
QLOG logging infrastructure - impl - framework #210
Comments
Blocked on #279 |
@hlandau I believe the block can be removed. We must have this feature in master, although with a proper disclaimer. IIRC, we discussed this only at the WG call; it is important to communicate this to @openssl/otc and see if there are no objections. |
My preferred route to do this is via openssl/general-policies#59, and feedback there is still desired. If we do not have the ability to make that happen, or make it happen rapidly enough, it's certainly true we can make this happen. Experimental features would be my preferred route. But there are some other options to manage the risk/instability. |
This is not an experimental feature - it is a core feature that we need to have in the release and need to have it available. |
If the format is changing then in my view it's the very definition of an experimental feature. "Not having it available by default" is the entire point of this. "If the QLOG spec updates we will follow it" — this doesn't even implement the current draft version of the QLOG spec. It deliberately implements the prior draft version of the QLOG spec because that's the version currently supported by QVIS. In other words I chose to implement the version QVIS supports rather than the current state of the I-D. It is correct that it is a question of how feature stability is communicated. That is the entire reason for the proposed policy. |
PR openssl/openssl#22037 is ready for review. Marking this as done. |
openssl/openssl#22037 has merged. |
No description provided.
The text was updated successfully, but these errors were encountered: