[Developer Guide Audit] Release

[mrbobbytables]

Documentation is the go-to reference for contributors. Parts of the developer guide have been cited as vastly out of date (e.g. referencing VERY outdated versions of docker). We are asking each SIG that owns a portion of the developer guide to audit their devel guide documentation.

This does not have to include updating it.
(although if you want to, please go ahead 😄 )

If you could, update this issue with items that are out of date or you think should be added to the release portion of the devel guide.

Assigning to leads, but please feel free to re-assign and delegate.
/assign @justaugustus @tpepper @alejandrox1 @saschagrunert

---

Parent Tracking Issue: #5229
/sig release
/sig contributor-experience
/area developer-guide
/milestone v1.20

[justaugustus]

I started some work by moving the version markers doc here: #5268

@kubernetes/sig-release-leads -- who's interested in driving the audit of our docs?

[justaugustus]

Also assigning Lauri!
/assign @LappleApple

[lasomethingsomething]

/assign @hasheddan

[justaugustus]

Assigning Savitha as discussed in today's SIG Release meeting.

/assign @savitharaghunathan
/unassign @justaugustus @tpepper @saschagrunert @hasheddan @LappleApple @alejandrox1

[justaugustus]

@savitharaghunathan -- any updates on this one?

[savitharaghunathan]

@savitharaghunathan -- any updates on this one?

Apologies for not progressing on this issue. It fell off my plate. I will get to it this weekend.

[jeremyrickard]

@savitharaghunathan can you pick up or re-assign to someone on release team or new contributor?

[savitharaghunathan]

/unassign
I would be happy to provide context and guidance if any contributor wants to pick this up.

[jeremyrickard]

/cc @Verolop

[jeremyrickard]

We will try and address this during 1.23

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[saschagrunert]

/remove-lifecycle stale

We will try and address this during 1.23

Did we finish that in 1.23?

[justaugustus]

Did we finish that in 1.23?

We currently have no assignee here. Assigning Jeremy, since he was the last to comment on this. :)
/assign @jeremyrickard
/milestone v1.24
/priority important-soon

[jeremyrickard]

@savitharaghunathan I will pick this up and get it moving forward. I'll reach out on slack to do a handoff/context transfer if that is ok.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[saschagrunert]

@jeremyrickard can this one be closed?

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[saschagrunert]

/close

[k8s-ci-robot]

@saschagrunert: Closing this issue.

In response to this:

/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.