Re: Proposal: Not shipping prefixed APIs on the release channel
On Thu, Dec 13, 2012 at 10:11 PM, Anthony Jones ajo...@mozilla.com wrote: Perhaps we could come up with an API for exposing experimental features? To go back to an earlier part of this thread: If you expose something on the release channel to Web authors, you are de facto releasing the feature for Web authors to bake into their sites/apps and risking it getting stuck in the sense that breaking changes cause a bad end user experience of sites/apps breaking. A moz prefix does not change that. Having to call enableExperimentalFeature() won’t change that. Writing documentation that says the feature is experimental won’t change that. enableExperimentalFeature(feature, version) As with version suffixing, there is a very real risk that removing old versions will break too much content and so old versions stick around forever. In that case, the same kind of considerations as those stated in http://lists.w3.org/Archives/Public/public-html/2007Apr/0279.html and http://robert.ocallahan.org/2008/01/http-equiv_22.html apply. -- Henri Sivonen hsivo...@iki.fi http://hsivonen.iki.fi/ ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
No more cycle collections during shutdown (opt builds)
Hi all, I just landed the patch for https://bugzilla.mozilla.org/show_bug.cgi?id=818739 in order to speed up shutdown times. Shutdown cycle collections are still run in debug builds so that we can detect leaks. Also, one can set XPCOM_CC_RUN_DURING_SHUTDOWN env variable to enable shutdown cycle collections in opt builds - can be useful when debugging leaks and such. If you see regressions, please file new bugs and make them block bug 818739. Regressions mean probably that we have code which is trying to do I/O too late. Based on https://bugzilla.mozilla.org/show_bug.cgi?id=818739#c17 such I/O shouldn't happen in normal cases. -Olli ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Enabling Telemetry by default on Aurora and Nightly
(cross posted to governance@ and privacy@) As I discussed during last week's development meeting and this week's coordination meeting, this post is to inform you of the intent to enable Telemetry by default on the Aurora and Nightly channels. This is a change that I first discussed back in Feb 2012 [1], and that may land as soon as Dec. 19, 2012. Most users on Firefox Nightly and Firefox Aurora are developers and highly technical users who actively contribute to help us build a more excellent browser by providing us with feedback. Enabling Telemetry by default on these channels makes it easier for them to do so by allowing Mozilla to better identify new issues and regressions early in the development cycle and make Firefox a better product. We've carefully considered all of the implications of making this change and teams across Mozilla have been engaged throughout the process. Enabling Telemetry by default in these channels is consistent with user expectations associated with helping us fully test and evaluate new versions of Firefox. We'll provide notice to users of the change via multiple means and disabling Telemetry will be a simple process. More details about this change and the rationale have been summarized in this FAQ: https://wiki.mozilla.org/Telemetry/faq Please respond with questions and comments to dev-platform. Lawrence [1] https://wiki.mozilla.org/Firefox/Planning/2012-02-01 ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Enabling Telemetry by default on Aurora and Nightly
On 12/14/12 7:15 PM, Lawrence Mandel wrote: ... intent to enable Telemetry by default on the Aurora and Nightly channels ... \o/ Justin ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
