Hi, We have made some changes on how we use milestones and labeling in hopes of making things clearer:
* Milestones are now used only for where an issue or pull request(PR) will be fixed/merged into. We used to use them for 'this affects version x'. This was confusing and did not work well as you can only have one milestone per ticket.. So we are now using them as actual milestones. * New labels have been introduces to let us indicate what versions of ansible does this issue or PR affect. affects_1.9 => this issue affects the 1.9 release * A new 'triage' label has been added, that will indicate that and issue or PR is awaiting to be looked at by a maintainer. This will mainly be used by our classification bot to signify that 'a human' has not looked at this yet, which until now was when an issue was 'unlabeled'. We hope these changes will make things clearer and help us get through the backlog faster. As always we welcome your feedback. ---------- Brian Coca Ansible Core Team -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
