-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
0.10 release planning #1528
Comments
That would be wonderful! 🙏 |
I'd like to include mechanics for enabling MTUD automatically where supported (some sort of
IIRC QUIC V2 is mainly an anti-ossification measure that won't impact public API. It'd be healthy for us to have it but I don't think it's pressing. Might bear a double-check.
I agree we're getting close, but if we're going to treat 1.0 as special we should probably defer a decision until we've actually not broken for a good while. Alternatively, we could abandon cosmetic concerns and just start bumping the major version without a care. |
Correct, see:
|
As long as |
As much as I'd love to get this merged finally, it doesn't need to be a blocker since it's not API-breaking, and can easily be included in a patch release. If it continues to be a difficult review it probably shouldn't delay the other more practically beneficial changes we have staged. |
We should probably get #1529 in before release. I think that's probably the only thing blocking the release at this point? |
I think so; I should be able to review that within the next few days. |
Since #1529 has been merged, should we plan to release 0.10? It looks like all the checkpoints have been resolved. |
Draft changelog:
Documentation
Internal improvements
|
This is a bit confusing as a literal changelog entry because in 0.9 the parameter was called
This is purely internal. LGTM otherwise! |
Time to start talking about the next semver-incompatible release, I guess?
We definitely want to wait for:
Other things to consider:
Should we consider bumping the next version to 1.0? Our API has been pretty stable...
The text was updated successfully, but these errors were encountered: