diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-07-25 15:12:56 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-07-25 15:12:56 -0700 |
| commit | 3642cd980e6c6fabd9a9482cb57329f792faa2d9 (patch) | |
| tree | 50825296759e0536cf8986c9edd854fd5c4765bb | |
| parent | 4c0c2e9e659d2f989f3d23c3634c16bb099f3064 (diff) | |
| parent | 0e31a17666866252d0e6d3bd2f9090627cd357aa (diff) | |
Merge pull request #2406 from spiffxp/kind-failing-test
Remove mentions of priority/failing-test
| -rw-r--r-- | contributors/guide/issue-triage.md | 11 |
1 files changed, 4 insertions, 7 deletions
diff --git a/contributors/guide/issue-triage.md b/contributors/guide/issue-triage.md index 6eacc9f1..76c7a82d 100644 --- a/contributors/guide/issue-triage.md +++ b/contributors/guide/issue-triage.md @@ -64,7 +64,7 @@ Support requests should be directed to the following: ### User support response example -If you see support questions on kubernetes-dev@googlegroups.com or issues asking for +If you see support questions on kubernetes-dev@googlegroups.com or issues asking for support try to redirect them to Stack Overflow. Example response: ```code @@ -82,7 +82,7 @@ large volume of support issues on github is making it difficult for us to use issues to identify real bugs. Members of the Kubernetes community use Stack Overflow to field support -requests. Before posting a new question, please search Stack Overflow for answers +requests. Before posting a new question, please search Stack Overflow for answers to similar questions, and also familiarize yourself with: * [user documentation](https://kubernetes.io/docs/home/) @@ -138,9 +138,6 @@ priority, in their area are being actively worked on. Examples include user-visible bugs in core features, broken builds or tests and critical security issues. -- **priority/failing-test**: Automatically filed frequently failing test. Needs -to be investigated. - - **priority/important-soon**: Must be staffed and worked on either currently, or very soon, ideally in time for the next release. @@ -201,8 +198,8 @@ bug shouldn't be in this milestone for more than a day or two towards the end of a milestone. It should be triaged either into vX.Y, or moved out of the release milestones. -The above [priority](#define-priority) scheme still applies. The `priority/critical-urgent` -and `priority/failing-test` issues are work we feel must get done before +The above [priority](#define-priority) scheme still applies. The +`priority/critical-urgent` issues are work we feel must get done before release. The `priority/important-soon` and `priority/important-longterm` issues are work we would merge into the release if it gets done, but we wouldn't block the release on it. A few days before release, we will probably move all |