|
| 1 | +.. _triaging: |
| 2 | + |
| 3 | +Triaging Issues and Pull Requests |
| 4 | +================================= |
| 5 | + |
| 6 | +.. note:: |
| 7 | + |
| 8 | + This document serves mainly as a reference for the NAPALM maintainers, |
| 9 | + but the users are equally welcome to read this document and understand our |
| 10 | + process, and eventually suggest improvements. |
| 11 | + |
| 12 | +We triage Issues and Pull Requests (PR) using GitHub features only: |
| 13 | + |
| 14 | +- :ref:`triage-labels` |
| 15 | +- :ref:`triage-milestone` |
| 16 | +- :ref:`triage-projects` |
| 17 | + |
| 18 | +.. _triage-labels: |
| 19 | + |
| 20 | +Labels |
| 21 | +++++++ |
| 22 | + |
| 23 | +.. _triage-driver-labels: |
| 24 | + |
| 25 | +Driver labels |
| 26 | +------------- |
| 27 | + |
| 28 | +Each platform supported by NAPALM has associated a label, e.g., ``junos``, ``eos``, |
| 29 | +``ios``, ``iosxr``, ``vyos``, etc. It is mandatory that the maintainer to apply |
| 30 | +one or more of these labels. |
| 31 | + |
| 32 | +.. _triage-api-change-label: |
| 33 | + |
| 34 | +``api change`` |
| 35 | +-------------- |
| 36 | + |
| 37 | +If the Issue would imply a change in the API, or the PR introduces changes in |
| 38 | +the API. By API change we refer to changes in the getters output structure, |
| 39 | +methods signature, or any core changes that must be uniformly introduced across |
| 40 | +all the drivers. |
| 41 | + |
| 42 | +.. _triage-awesome-label: |
| 43 | + |
| 44 | +``awesome`` |
| 45 | +----------- |
| 46 | + |
| 47 | +When someone adds or proposes something really awesome. |
| 48 | + |
| 49 | +.. _triage-base-label: |
| 50 | + |
| 51 | +``base`` |
| 52 | +-------- |
| 53 | + |
| 54 | +When base components are affected, e.g., `get_network_driver`, the validate |
| 55 | +functionality, or the testing framework. |
| 56 | + |
| 57 | +.. _triage-blocked-label: |
| 58 | + |
| 59 | +``blocked`` |
| 60 | +----------- |
| 61 | + |
| 62 | +Added in case we block the PR temporarly, or an Issue is currently blocked by |
| 63 | +other internal or external factors (PRs pending to be merged, other bugs to be |
| 64 | +solved a priori, etc.) |
| 65 | + |
| 66 | +.. _triage-bug-label: |
| 67 | + |
| 68 | +``bug`` |
| 69 | +------- |
| 70 | + |
| 71 | +Whenever the behaviour reported in the Issue is different than it should, or the |
| 72 | +PR kills a bug. |
| 73 | + |
| 74 | +.. _triage-cannot-reproduce: |
| 75 | + |
| 76 | +``cannot reproduce`` |
| 77 | +-------------------- |
| 78 | + |
| 79 | +This refers to Issues only, and it is added when the maintainer(s) cannot |
| 80 | +reproduce the behaviour reported. |
| 81 | + |
| 82 | +.. _triage-core-label: |
| 83 | + |
| 84 | +``core`` |
| 85 | +-------- |
| 86 | + |
| 87 | +When any core components (drivers) are affected. |
| 88 | + |
| 89 | +.. _triage-deprecation-label: |
| 90 | + |
| 91 | +``deprecation`` |
| 92 | +--------------- |
| 93 | + |
| 94 | +Added only to PRs, when a API deprecation is introduced. |
| 95 | + |
| 96 | +.. _triage-documentation-label: |
| 97 | + |
| 98 | +``documentation`` |
| 99 | +----------------- |
| 100 | + |
| 101 | +Can be added to both Issues and PRs, anything related to the documentation. |
| 102 | + |
| 103 | +.. _triage-duplicate-label: |
| 104 | + |
| 105 | +``duplicate`` |
| 106 | +------------- |
| 107 | + |
| 108 | +Applicable to Issues only, to be added before closing a duplicate. |
| 109 | + |
| 110 | +.. _triage-feature-label: |
| 111 | + |
| 112 | +``feature`` |
| 113 | +----------- |
| 114 | + |
| 115 | +When a new feature is introduced, or the user requests a new feature. |
| 116 | + |
| 117 | +.. _triage-good-first-issue: |
| 118 | + |
| 119 | +``good first issue`` |
| 120 | +-------------------- |
| 121 | + |
| 122 | +While we want to encourage the community to contribute more and more frequent, |
| 123 | +many engineers are still afraid of complex tasks. This label marks simple fixes |
| 124 | +that new contributors can address. It is recommended that this label to be |
| 125 | +accompanied by an explanation and a pointer for the new contributors. |
| 126 | + |
| 127 | +.. _triage-help-wanted: |
| 128 | + |
| 129 | +``help wanted`` |
| 130 | +--------------- |
| 131 | + |
| 132 | +This marks an Issue were we ask the community for help, or we need more details |
| 133 | +on a particular topic (e.g., outputs from different platforms, explanation, etc.) |
| 134 | +from any volunteer from the community. |
| 135 | + |
| 136 | +Once we have all the details required, the maintainer has to remove this label |
| 137 | +even though it does not start working on it immediately. |
| 138 | + |
| 139 | +.. _triage-high-severity-label: |
| 140 | + |
| 141 | +``high severity`` |
| 142 | +----------------- |
| 143 | + |
| 144 | +Whenever a :ref:`triage-bug-label` affects severely one or more features, making |
| 145 | +it basically unusable. |
| 146 | + |
| 147 | +.. _triage-info-needed-label: |
| 148 | + |
| 149 | +``info needed`` |
| 150 | +--------------- |
| 151 | + |
| 152 | +We add this label when we need more details and further explanation from the user |
| 153 | +that reports an Issue. Once we received everything needed, we can remove that |
| 154 | +label. |
| 155 | + |
| 156 | +.. _triage-investigation-label: |
| 157 | + |
| 158 | +``investigation`` |
| 159 | +----------------- |
| 160 | + |
| 161 | +We need to investigate the problem further. |
| 162 | + |
| 163 | +.. _triage-new-driver: |
| 164 | + |
| 165 | +``new driver`` |
| 166 | +-------------- |
| 167 | + |
| 168 | +When we discuss the possibility to add a new core driver. |
| 169 | + |
| 170 | +.. _triage-new-method: |
| 171 | + |
| 172 | +``new method`` |
| 173 | +-------------- |
| 174 | + |
| 175 | +When we discuss the possibility or implement a new method to one or more drivers. |
| 176 | +The method does not necessarily need to be a completely new one to NAPALM. |
| 177 | + |
| 178 | +.. _triage-vendor-bug-label: |
| 179 | + |
| 180 | +``vendor bug`` |
| 181 | +-------------- |
| 182 | + |
| 183 | +When the bug is casued by a vendor stupidity. |
| 184 | + |
| 185 | +.. _triage-milestone: |
| 186 | + |
| 187 | +Milestone |
| 188 | ++++++++++ |
| 189 | + |
| 190 | +The milestones are used to group the Issues and the Pull Requests from a |
| 191 | +different angle: |
| 192 | + |
| 193 | +.. _triage-version-milestone: |
| 194 | + |
| 195 | +Version |
| 196 | +------- |
| 197 | + |
| 198 | +The Issue will be solved, or the PR will be included in this release. |
| 199 | + |
| 200 | +.. _triage-approved-milestone: |
| 201 | + |
| 202 | +``APPROVED`` |
| 203 | +------------ |
| 204 | + |
| 205 | +It means that we accept the Issue or the PR, but we don't have a schedule yet |
| 206 | +for when the Issue will be solved, or the PR will be included in a release. |
| 207 | + |
| 208 | +.. _triage-blocked-milestone: |
| 209 | + |
| 210 | +``BLOCKED`` |
| 211 | +----------- |
| 212 | + |
| 213 | +This groups the Issues or the PRs we could not accept for the reasons marked |
| 214 | +using the labels. |
| 215 | + |
| 216 | +.. _triage-discussion-milestone: |
| 217 | + |
| 218 | +``DISCUSSION`` |
| 219 | +-------------- |
| 220 | + |
| 221 | +The Issue or the PR needs further discussion. |
| 222 | + |
| 223 | + |
| 224 | +.. _triage-projects: |
| 225 | + |
| 226 | +Projects |
| 227 | +++++++++ |
| 228 | + |
| 229 | +Any major change that may consist on several Pull Requests should be groupped |
| 230 | +into a GitHub Project. |
| 231 | + |
0 commit comments