On 4/10/13 1:53 PM, Alex Keybl wrote:
Knowing this, why not consider just using the status-flags purely
to track landings and let the team determine how to use target
milestone? Also, why not set the status-flag in general for the
appropriate Firefox release when a patch lands on trunk?
The difference between version-specific status flags (fixed) and
target milestone (along with resolved/fixed) is subtle. [...]
Sounds like there are some details to sort out, but I rather like the
idea. I _still_ see people confused about what "target milestone" is,
and having a consistent mechanism for what gets set for a m-c landing vs
aurora/beta would sure be nice. Scripts or pseudoflags whose actual
value is derived from other things might be of use.
I'd question if we really need to keep Target Milestone at all (given
replacements for how it's used now). I don't see many Firefox/Gecko
teams using it (let alone consistently). The whiteboard should be
adequate for indicating aspirational landings.
There is _significant_ value in eliminating/replacing niche workflows in
favor of a more consistent system that people can actually understand.
Justin
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
