keith-turner commented on a change in pull request #396: Proposal for switching to github issues URL: https://github.com/apache/accumulo/pull/396#discussion_r172627407
########## File path: CONTRIBUTING.md ########## @@ -17,7 +17,24 @@ limitations under the License. # Contributors Guide - If you believe that you have found a bug, please search for an existing [issue](https://issues.apache.org/jira/browse/accumulo) to see if it has already been reported. If you would like to add a new feature to Accumulo, please send an email with your idea to the [dev](mailto:d...@accumulo.apache.org) mail list. If it's appropriate, then we will create a ticket and assign it to you. + If you believe that you have found a bug, please search for an existing [issue](https://github.com/apache/accumulo/issues) to see if it has already been reported. If you would like to add a new feature to Accumulo, please send an email with your idea to the [dev](mailto:d...@accumulo.apache.org) mail list. If it's appropriate, then we will create a ticket and assign it to you. + +## Issues + +For pull request and issues, the following labels are used. Consider an issue +with labels `v1.9.3`, `v2.0.2`, and `bug`. If the issue is open, then its a +bug that someone plans to fix in 1.9.3 and 2.0.2. If it is closed, then +it was fixed in those versions. + + Label | Description +-------------|---------------------------------------------------------------------------- + blocker | Indicates a release blocker that must be fixed in labeled versions. + bug | + duplicate | + enhancement | + vX.Y.Z | Fix version. The prefix `v` was chosen so that these labels sort last in the drop down list. Review comment: I considered having tags for affects version, but decided not to in this initial proposal. If you are using 1.7.2 and want to know what bugs may affect it, then it would be best to query for `fixVersion in (1.7.3,1.7.4)` rather than `affectsVersion=1.7.2`. The reason is I think the affects version in JIRA is not well maintained. For example when an issue is fixed in 1.7.4 and affects 1.7.3, 1.7.2, .1.7.1, and 1.7.0 it may only have 1.7.3 filled in for affects version in JIRA. I also thought about the priority levels in JIRA and it seems all of them are very subjective except for blocker. Ciritical, trivial, etc seem to mean different things to different people and have no well defined actionable meaning within the project. However blocker does seem to have a well defined actionable meaning, it means someone wants the release to wait for this fix. That is why blocker is the only priority level I carried over from JIRA in the initial proposal. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
