Comment 2 for bug 2055171

Noting that there's also a procedural change to consider to reduce the manual work required (and/or reduce the changes of hitting API limits): assign specific milestones only at the point where it is nigh certain that a fix will make it into that release.

In practice, I think that boils down to the committer making the assignment at the point of merging the change or somebody making a commitment to shepherd the bugfix over the next few days.

Doing this would also reduce the overall email churn, whether or not somebody filters out Bugmaster mail or not.

Targeting to series without selecting a milestone could continue to be a way of making assertions about the affected versions for a bug or requesting backports to maintenance versions.