| Andrew Gerrand | 5bc444d | 2014-12-10 11:35:11 +1100 | [diff] [blame] | 1 | This document explains how we handle issue triage and scheduling in [the Go project's issue tracker](http://golang.org/issue). |
| 2 | |
| 3 | # New issues |
| 4 | |
| 5 | All new issues are created with status "New" and no other labels. |
| 6 | |
| 7 | When an issue is changed from "New" to "Accepted" (or any open state): |
| 8 | * Mark it with a Release-**label (see below). |
| 9 | * Add a sentence that describes the rationale for the label.** |
| 10 | |
| 11 | If you're a committer creating an issue, you can change it from “New” to “Accepted” while filing the issue, but if you do, be sure to add a Release-**label and a rationale.** |
| 12 | |
| 13 | # Release Labels |
| 14 | |
| 15 | Any issue planned for a specific release (or explicitly not planned for a release) must have one of these labels: |
| 16 | |
| 17 | * Release-Go1.3 - must be addressed (and probably fixed) for Go 1.3 |
| 18 | * Release-Go1.3Maybe - would be nice if it were addressed for Go 1.3 |
| 19 | * Release-Go1.4 - will be re-examined for the next release |
| 20 | * Release-None - no plan to fix in any specific release |
| 21 | |
| 22 | # Dashboards |
| 23 | |
| 24 | * [Status-New](http://research.swtch.com/dashboard/Status-New) |
| 25 | |
| 26 | * [Release-Go1.3](http://research.swtch.com/dashboard/Go1.3) |
| 27 | * [Release-Go1.4](http://research.swtch.com/dashboard/Go1.4) |
| 28 | * [Release-None](http://research.swtch.com/dashboard/Release-None) |
| 29 | |
| 30 | # Nominating an issue |
| 31 | |
| 32 | If you're not a committer and you would like an issue to be addressed in Go 1.3, please: |
| 33 | * Leave a comment on the issue explaining why, |
| 34 | * Include the hashtag "#go13" in the comment. |
| 35 | Committers were periodically look at the issues with #go13 comments and adjust their status accordingly. |
