FWIW to bring more information into here on alternative target milestone use that I talked with Ed about.
The AMO and Marketplace team is an example group that actually uses the target milestone field for the "aspirational" landing that's described above to plot what fixes they are trying to get in within the next weekly release or something that has a defined date. If a patch misses the target date, then they alter the target milestone fields respectively for the next "aspirational" landing. After the fix lands, then the target milestone reflects what weekly release the patch landed on. On B2G, we went through a phase where the target milestone field was being used for convergence milestone planning to phase out what bugs should be fixed in what order. In this case, the target milestone field was used in the context for "aspirational" landing for planning purposes. So I wouldn't necessarily throw out the fact that aspirational landing concept usage with target milestone doesn't exist. In fact, there's more than enough cases I've seen that has warranted usage for it. I have the seen the case where whiteboards were used instead, however. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
