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.

Sign up for GitHub

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

Jump to bottom

Refresh documentation and blog posts for the package repositories (pkgs.k8s.io) #3878

Open
xmudrii opened this issue Jan 6, 2025 · 1 comment
Open

Refresh documentation and blog posts for the package repositories (pkgs.k8s.io) #3878

xmudrii opened this issue Jan 6, 2025 · 1 comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@xmudrii
Copy link
Member

xmudrii commented Jan 6, 2025

We should go through all documents and blog posts mentioning the package repositories to make sure they reflect the current state of the world. There might be several important documents that are out of date. We also talked about refreshing the blog post and potentially publishing a new one that recaps our efforts.

/kind documentation
/sig release
/triage accepted
/priority important-soon
@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. sig/release Categorizes an issue or PR as relevant to SIG Release. triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jan 6, 2025
This was referenced Jan 6, 2025
Closed
Closed
@xmudrii
Copy link
Member Author

xmudrii commented Jan 6, 2025

We need to make sure we document how to refresh the GPG key once expired/needed: #3840

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
SIG Release - Packaging
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xmudrii @k8s-ci-robot