On 4/25/16 1:47 AM, Jet Villegas wrote:
The "Intent to Implement" should help some of the concerns and allow for comments. "Intent to Ship" usually means (at least for Platform Rendering) that we'll be removing the #ifndef RELEASE flags and enabling preferences. That is, by the time the "Intent to Ship" e-mail is sent, fundamental issues should have already been resolved with module owners and other parties.
It seems to me that "Intent to Implement" is mostly about "is this possibly a good idea at all?" and may well not involve a thorough API review (because the API may well change as a result of implementor feedback during implementation) nor a thorough consideration of web compat (because there is no data yet), what other UAs are doing (because it doesn't matter that much at that early stage), or the actual state of the feature in relation to our codebase (because it's not known yet).
An "Intent to Ship" should consider all of the above; it's a much higher bar.
That said, note that a bunch of the items above lie somewhat out of a specific module, so it's not clear to me that we want intent-to-ship OKs to be module-specific.
-Boris _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
