Deprecate and spin down net-http01
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.
- [x] Send out notice - https://groups.google.com/g/knative-dev/c/dANda64Pvqg
- [x] Update release notes
- [x] Update README.md on net-http01 repo marking deprecation and archive dates
- https://github.com/knative-extensions/net-http01/pull/568
- [x] Drop from release train
- https://github.com/knative/release/pull/265
- [x] Drop from downstream tests
- [x] https://github.com/knative/pkg/pull/2968
- [x] https://github.com/knative/networking/pull/930
- [x] Update Website
- [x] remove net-http01 integration in main
- https://github.com/knative/docs/pull/5761
- [x] mark net-http01 integration deprecated in v1.11 and v1.12 branches
- https://github.com/knative/docs/pull/5762
- [x] remove net-http01 integration in main
v1.12 EOL (2024-04-30)
- [ ] Close all issues & PRs in net-http01
- [ ] Archive repo via peribolos (update knative/community)
- [ ] Drop prow jobs
- [x] Drop repo from knobots - https://github.com/knative-extensions/knobots/pull/366
cc @nak3 @ReToCode @skonto for input on timeline
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? https://github.com/knative/docs/pull/5761/files#diff-12992d159bc1329670548661400eea0c1c297f55cdee53f2d2b0855e367f3743
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
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
/remove-lifecycle stale
All outstanding PRs are out