Blog Issue triage (#11371)
* Blog Issue triage SIG-Docs decided that we only maintain blog entires <1 year in age. Updating our triage guidelines to reflect this. * Fix typo, link markup, two misplaced modifiers
This commit is contained in:
@@ -37,7 +37,7 @@ that one person does all of them all of the time.
|
|||||||
In any given week, a specific docs approver volunteers to do initial triage
|
In any given week, a specific docs approver volunteers to do initial triage
|
||||||
and review of [pull requests and issues](#triage-and-categorize-issues). This
|
and review of [pull requests and issues](#triage-and-categorize-issues). This
|
||||||
person is the "PR Wrangler" for the week. The schedule is maintained using the
|
person is the "PR Wrangler" for the week. The schedule is maintained using the
|
||||||
[PR Wrangler scheduler(https://github.com/kubernetes/website/wiki/PR-Wranglers).
|
[PR Wrangler scheduler](https://github.com/kubernetes/website/wiki/PR-Wranglers).
|
||||||
To be added to this list, attend the weekly SIG Docs meeting and volunteer. Even
|
To be added to this list, attend the weekly SIG Docs meeting and volunteer. Even
|
||||||
if you are not on the schedule for the current week, you can still review pull
|
if you are not on the schedule for the current week, you can still review pull
|
||||||
requests (PRs) that are not already under active review.
|
requests (PRs) that are not already under active review.
|
||||||
@@ -527,7 +527,7 @@ In any given week, a specific docs approver volunteers to do initial
|
|||||||
on this list, attend the weekly SIG Docs meeting and volunteer. Even if you are
|
on this list, attend the weekly SIG Docs meeting and volunteer. Even if you are
|
||||||
not on the schedule for the current week, you can still review PRs.
|
not on the schedule for the current week, you can still review PRs.
|
||||||
|
|
||||||
People in SIG Docs are only responsible for triaging and categorizing
|
People in SIG Docs are responsible only for triaging and categorizing
|
||||||
documentation issues. General website issues are also filed in the
|
documentation issues. General website issues are also filed in the
|
||||||
`kubernetes/website` repository.
|
`kubernetes/website` repository.
|
||||||
|
|
||||||
@@ -625,6 +625,13 @@ resolve the issue. Dead links in the API and Kubectl docs are automation issues
|
|||||||
and should be assigned a P1 until the problem can be fully understood. All other
|
and should be assigned a P1 until the problem can be fully understood. All other
|
||||||
dead links are issues that need to be manually fixed and can be assigned a P3.
|
dead links are issues that need to be manually fixed and can be assigned a P3.
|
||||||
|
|
||||||
|
#### Blog issues
|
||||||
|
|
||||||
|
[Kubernetes Blog](https://kubernetes.io/blog/) entries are expected to become
|
||||||
|
outdated over time, so we maintain only blog entries that are less than one year old.
|
||||||
|
If an issue is related to a blog entry that is more than one year old, it should be closed
|
||||||
|
without fixing.
|
||||||
|
|
||||||
#### Support requests or code bug reports
|
#### Support requests or code bug reports
|
||||||
|
|
||||||
Some issues opened for docs are instead issues with the underlying code, or
|
Some issues opened for docs are instead issues with the underlying code, or
|
||||||
|
|||||||
Reference in New Issue
Block a user