> The pain comes from issues marked for a bug release milestone but it is > merged directly to master and never cherry-picked to branch for bugfix > releases. > So the release manager has to compare branches and master and also have to > compare labels, milestones and even look into the details of pull requests > to understood whether a change is cherry-picked or not.
This is a problem, but it should be 99% automatable. In fact it should be automated, that before cutting a release, that we have a script that validates that all issues labelled for the release have a change present in the commit log, and all commit log messages are referenced by some issue or PR. Gerrit has a change-id that makes this easy, but I'm not sure about github. -Ivan
