@@ -13,7 +13,7 @@ A well organized repo allows maintainers to prioritize feature requests, fix bug
Triage includes:
- Labeling issues
- Responding to issues
- Closing issues (under certain circumstances!)
- Closing issues
If you're interested in helping out with minikube triage, this doc covers the basics of doing so.
...
...
@@ -29,7 +29,7 @@ The list of outstanding items are at https://teaparty-tts3vkcpgq-uc.a.run.app/s/
1. Issues without a `kind/` or `triage/` label
1. Issues without a `priority/` label
1.`triage/needs-information` issues which the user has followed up on
1.`triage/needs-information` issues which the user has followed up on, and now require a response.
## Categorization
...
...
@@ -49,18 +49,23 @@ Other possibilities:
If the issue is specific to an operating system, hypervisor, container, addon, or Kubernetes component:
os/<operatingsystem> - When the issue appears specific to an operating system
**os/[operating system]** - When the issue appears specific to an operating system
-`os/linux`
-`os/macos`
-`os/windows`
co/<driver> - When the issue appears specific to a driver
**co/[driver]** - When the issue appears specific to a driver
-`co/hyperkit`
-`co/hyperv`
-`co/kvm2`
-`co/none-driver`
-`co/docker-driver`
-`co/virtualbox`
co/<kubernetescomponent> - When the issue appears specific to a k8s component
**co/[kubernetes component]** - When the issue appears specific to a k8s component
-`co/apiserver`
-`co/etcd`
-`co/coredns`
...
...
@@ -74,16 +79,21 @@ co/<kubernetes component> - When the issue appears specific to a k8s component
Other useful tags:
Did an **Event** occur that we can dedup similar issues against?
-`ev/CrashLoopBackoff`
-`ev/Panic`
-`ev/Pending`
-`ev/kubeadm-exit-1`
Suspected **Root cause**:
-`cause/vm-environment`
-`cause/invalid-kubelet-options`
**Help wanted?**
`Good First Issue` - bug has a proposed solution, can be implemented w/o further discussion.
`Help wanted` - if the bug could use help from a contributor
...
...
@@ -132,26 +142,27 @@ This includes reviewing:
### Needs More Information
A sample response to ask for more info:
```
I don’t yet have a clear way to replicate this issue. Do you mind adding some additional details? Here is additional information that would be helpful:
* The exact `minikube start` command line used
* The full output of the `minikube start` command, preferably with `--alsologtostderr -v=4` for extra logging.
* The full output of `minikube logs`
* The full output of `kubectl get po -A`
> I don’t yet have a clear way to replicate this issue. Do you mind adding some additional details. Here is additional information that would be helpful:
>
> \* The exact `minikube start` command line used
>
> \* The full output of the `minikube start` command, preferably with `--alsologtostderr -v=4` for extra logging.
>
> \* The full output of `minikube logs`
>
> \* The full output of `kubectl get po -A`
>
>
>
> Thank you for sharing your experience!
Thank you for sharing your experience!
```
Then: Label with `triage/needs-information`.
### Issue might be resolved
If you think a release may have resolved an issue, ask the author to see if their issue has been resolved:
```
Could you please check to see if minikube <x> addresses this issue? We've made some changes with how this is handled, and improved the minikube logs output to help us debug tricky cases like this.
```
> Could you please check to see if minikube <x> addresses this issue? We've made some changes with how this is handled, and improved the minikube logs output to help us debug tricky cases like this.
Then: Label with `triage/needs-information`.
...
...
@@ -169,40 +180,39 @@ In any of these situations, we aim to be kind when closing the issue, and offer
Samples responses for these situations include:
### Issue has been addressed
```
@author: I believe this issue is now addressed by minikube v1.4, as it <reason>. If you still see this issue with minikube v1.4 or higher, please reopen this issue by commenting with `/reopen`
Thank you for reporting this issue!
```
>@author: I believe this issue is now addressed by minikube v1.4, as it <reason>. If you still see this issue with minikube v1.4 or higher, please reopen this issue by commenting with `/reopen`
>
>Thank you for reporting this issue!
Then: Close the issue
### Duplicate Issue
```
This issue appears to be a duplicate of #X, do you mind if we move the conversation there?
This way we can centralize the content relating to the issue. If you feel that this issue is not in fact a duplicate, please re-open it using `/reopen`. If you have additional information to share, please add it to the new issue.
Thank you for reporting this!
```
>This issue appears to be a duplicate of #X, do you mind if we move the conversation there?
>
>This way we can centralize the content relating to the issue. If you feel that this issue is not in fact a duplicate, please re-open it using `/reopen`. If you have additional information to share, please add it to the new issue.
>
>Thank you for reporting this!
Then: Label with `triage/duplicate` and close the issue.
### Lack of Information
If an issue hasn't been active for more than four weeks, and the author has been pinged at least once, then the issue can be closed.
```
Hey @author -- hopefully it's OK if I close this - there wasn't enough information to make it actionable, and some time has already passed. If you are able to provide additional details, you may reopen it at any point by adding /reopen to your comment.
Here is additional information that may be helpful to us:
* Whether the issue occurs with the latest minikube release
* The exact `minikube start` command line used
* The full output of the `minikube start` command, preferably with `--alsologtostderr -v=3` for extra logging.
* The full output of `minikube logs`
Thank you for sharing your experience!
```
>Hey @author -- hopefully it's OK if I close this - there wasn't enough information to make it actionable, and some time has already passed. If you are able to provide additional details, you may reopen it at any point by adding /reopen to your comment.
>
>Here is additional information that may be helpful to us:
>
>\* Whether the issue occurs with the latest minikube release
>
>\* The exact `minikube start` command line used
>
>\* The full output of the `minikube start` command, preferably with `--alsologtostderr -v=3` for extra logging.
