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

1.19-specific release notes URL #23855

Closed
bergerhoffer opened this issue Sep 13, 2020 · 11 comments
Closed

1.19-specific release notes URL #23855

bergerhoffer opened this issue Sep 13, 2020 · 11 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@bergerhoffer
Copy link

This is a Feature Request

What would you like to be added
A 1.19-specific URL for the Kubernetes 1.19 release notes.

Why is this needed

Currently, I can only find the 1.19 release notes at https://kubernetes.io/docs/setup/release/notes/. I assume that page will eventually be updated to be for 1.20 once that is released. So it would be nice to have a page to link to that will be "guaranteed" to stay as is for the 1.19 release notes.

We currently link to https://v1-18.docs.kubernetes.io/docs/setup/release/notes/ for 1.18, (and have used this format for past releases), but it doesn't look like there is one for 1.19.

Comments
Thanks!

@sftim sftim mentioned this issue Sep 14, 2020
7 tasks
@sftim
Copy link
Contributor

sftim commented Sep 14, 2020

/sig release
/kind feature

@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. kind/feature Categorizes issue or PR as related to a new feature. labels Sep 14, 2020
@sftim
Copy link
Contributor

sftim commented Sep 14, 2020

If https://v1-19.docs.kubernetes.io/docs/setup/release/notes/ were a redirect to https://kubernetes.io/docs/setup/release/notes/ until the next release happens, that might be good enough.

Or we could make that a general redirect to the live site with an exemption for the release notes pages.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 13, 2020
@bergerhoffer
Copy link
Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 14, 2020
@bergerhoffer
Copy link
Author

I do see that https://v1-19.docs.kubernetes.io/docs/setup/release/notes/ was added for 1.19 which is awesome.

However, since the generic link (https://kubernetes.io/docs/setup/release/notes/) was updated to 1.20, this means that our page that linked to 1.19 is now actually pointing to 1.20 release notes. This is the problem we foresaw when opening this issue. I'll go back and update our links, but it could be causing some confusion for readers in the meantime.

And I can see that we're going to keep running into the same problem for 1.20 (and further), which doesn't have a version-specific page yet. Would love to see the new release notes get their own version-specific page at the time it is released, like it used to. Then you could always have the generic link (https://kubernetes.io/docs/setup/release/notes/) redirect to the latest version's release notes.

@sftim
Copy link
Contributor

sftim commented Dec 14, 2020

@bergerhoffer I recommend tracking this as a part of issue #20293 - it's not specific to a particular release

@bergerhoffer
Copy link
Author

Thanks @sftim I've added a comment to that issue.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 14, 2021
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 13, 2021
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

No branches or pull requests

4 participants