Skip to content
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

Closed
14 tasks done
dprotaso opened this issue Nov 20, 2023 · 9 comments
Closed
14 tasks done

Deprecate and spin down net-http01 #14640

dprotaso opened this issue Nov 20, 2023 · 9 comments
Assignees
Milestone

Comments

@dprotaso
Copy link
Member

dprotaso commented Nov 20, 2023

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)

@dprotaso dprotaso added this to the v1.13.0 milestone Nov 20, 2023
@dprotaso
Copy link
Member Author

cc @nak3 @ReToCode @skonto for input on timeline

@dprotaso
Copy link
Member Author

dprotaso commented Nov 20, 2023

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.

@nak3
Copy link
Contributor

nak3 commented Nov 21, 2023

(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

@ReToCode
Copy link
Member

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.

@dprotaso
Copy link
Member Author

I'll update the release notes

@dprotaso dprotaso modified the milestones: v1.13.0, v1.15.0 Nov 22, 2023
@dprotaso
Copy link
Member Author

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.

Copy link

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.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 23, 2024
@ReToCode
Copy link
Member

/remove-lifecycle stale

@knative-prow knative-prow bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 23, 2024
@dprotaso
Copy link
Member Author

All outstanding PRs are out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants