At the Traffic Control summit, we discussed the need to do a better job scoping releases. What changes can I expect in an upcoming release? What changes went in to a completed release?
The only way I can think to do this (without having a release manager that actively manages the scope of a release) is to leverage Github labels and milestones on issues and PRs. For example, when creating an issue or a PR, make sure it has one or more component labels (Traffic Ops, Traffic Monitor, etc) on it at a minimum. If you are unable to attach labels, reach out to a "committer". They can add labels for you. Also, if you plan to work on an issue, make sure you assign it to yourself (or put a comment that you are working on it) and select the appropriate milestone. (again, ask a "committer" if you can't assign the milestone) By using labels and milestones, I think it should be pretty easy to see what is going in / went in to a particular release. thoughts? jeremy
