I'm sure there are other use cases, but the most common one for me is using it to sort out tracking flags for regressions and otherwise complicated dependency trees.
Gavin On Thu, Jan 9, 2014 at 9:53 AM, Chris Peterson <cpeter...@mozilla.com> wrote: > On 1/9/14, 7:17 AM, Kartikaya Gupta wrote: >> >> I think the "Target Milestone" field is poorly named, at least with >> respect to what we use it for. In practice this field is set to the >> version of m-c on which the patches originally landed, and doesn't >> change when patches are uplifted to other branches. > > > What is the use case for "Target Milestone" (in the "Patches Landed In" > sense)? As you point out, the Target Milestone is not updated if a fix is > uplifted, so Target Milestone does not even represent the first Gecko > release that contains the fix. That information would be useful. The > status-firefoxXX=fixed fields can do that now. > > Having a "Release We Would Like To Fix This Bug In" field might be useful > for project scheduling, but teams have (or are investigating) better project > planning tools outside of Bugzilla. So the current meaning of "Target > Milestone" does not seem very useful. > > Similarly, Bugzilla's "Priority" and "Severity" fields are ostensibly for > project planning, but these fields are rarely used. Their intent is also > better served by other project planning tools. > > > chris > > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
