wohali commented on issue #499: Sort out GitHub issues for gitbox repos URL: https://github.com/apache/couchdb/issues/499#issuecomment-299590828 The point of GitHub's milestones is to associate a milestone name, description, and optional due date with one or more issues. Milestones can also be open or closed. Typically I see milestones showing what work remains to get a release out the door - you get a nice little bargraph in the UI, for instance. But milestones could also be feature related. Tags don't give you the bar graph or due date, and the tag space can get cluttered quickly (we already have 30 tags to choose from.) I'm nominally against using tags to coordinate releases as a result. If we mirror what we've done in the past in JIRA, there are 2 scenarios where we've used the "Fixed in release" field that would match the GH Milestone function: 1. To show we've fixed a reported bug and that it'll be patched in the next release 2. To put a stake in the ground to say an issue is a release blocker In that way I'm in favour of porting over exactly those 2 scenarios from JIRA "Fixed in Release" to GH Milestones. ---------------------------------------------------------------- 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: [email protected]
With regards, Apache Git Services
