| | 115 | The following are GHC-specific policies for using the Trac bug tracking system. |
| | 116 | |
| | 117 | * When a bug is fixed, but the patch or patches still need to be merged to other branches, then |
| | 118 | don't close the bug, just change its type from "bug" or "task" to "merge". Also add a list of |
| | 119 | patches to be merged, and which branch to merge to, as a comment. |
| | 120 | |
| | 121 | * Milestones: we have milestones for each release, and three special milestones: |
| | 122 | * An empty milestone field means the bug has not been triaged yet. We don't yet know if the |
| | 123 | ticket is a real, unique, issue. Once this has been established, the ticket will be given |
| | 124 | a milestone. |
| | 125 | * '''Not GHC''' is for tickets that are not tied to a GHC release, because they are in libraries |
| | 126 | or other software that is not released with GHC. Bugs in the "extra libraries" typically fall |
| | 127 | into this category. |
| | 128 | * '''_|_''' is for tickets that have been triaged, but we don't plan to fix them for a particular |
| | 129 | release. This might be because the bug is low priority, or is simply too hard to fix right now. |
| | 130 | |
