-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Deprecate and spin down net-http01 #14640
Comments
I've updated the timeline to say we're supporting net-http01 until v1.12 goes EOL. Otherwise if we waited two releases for the notice and then waited until those releases EOL we'd be supporting this component for another year. Given that no one said they it I don't think that's necessary support for that long. |
(Deleted my previous comment) We need to update v1.12 release note, which was already published? I would like to avoid the change of previous release note as much as possible but I'll defer the decision to @dprotaso @ReToCode and @skonto |
Hm as nobody responded to be using it, I'd also vote not not release it for 1.13, as Dave also sent an email about it. I think it should be fine to update the past release notes, if the hint is formatted to be really visible. |
I'll update the release notes |
All the current work is done - moving to v1.15 milestone. After v1.14 is cut 1.12 is EOL so we should do the remaining work. |
This issue is stale because it has been open for 90 days with no |
/remove-lifecycle stale |
All outstanding PRs are out |
In the last Serving WG meeting we've decided to spin down the net-http01 integration.
We're announcing deprecation which means v1.12 will be the last release of net-http01. We continue to support the v1.11 and v1.12 release of this repo until they EOL.
v1.12 EOL (2024-04-30)
The text was updated successfully, but these errors were encountered: