Joe Drew schrieb:
On 2012-11-06 8:31 AM, Henri Sivonen wrote:
Therefore, I propose that we adopt the following policy:
  1) APIs that are not ready for use by Web developers shall not be
shipped on the release channel (unless preffed off).
  2) APIs that are shipped on the release channel shall be shipped
without a prefix.

I am broadly in support of this, but I have a specific concern: Firefox
OS will (or could) require experimental APIs that aren't fully baked
simply because of time constraints. I don't think we should hamstring
the features possible in FxOS to simply stabilize an API.

I would, however, be in favour of the result of s/release
channel/release channel on desktop/g.

I think we should have a pref that just turns on/off all the prefixed technologies, and ship with that on in the experimental channels and off on release (I'd say that beta is up for discussion, I'd lean towards off on beta as we treat beta as RC and want testing there to match release as much as possible so we don't get surprises when shipping).

This way, we can just ship B2G with that pref on as long as we require that (I hope it will get stable enough at some point so we can apply the same principles we're using elsewhere).

Robert Kaiser
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to