A number of us are now implementing features behind prefs rather than
using prefixes and, if the relevant specification is not far enough
advanced, disabling the features on Release and Beta. This is a manual
process and requires people to remember to get approval for and land a
pref twiddling patch on Aurora just before an uplift. Sometimes this
remembering does not happen.
Thanks to bug 820148, there is now a way to set preferences at compile
time based on whether we are building a Release/Beta or Aurora/Nightly.
You can write:
#ifdef RELEASE_BUILD
pref("my.preffable.feature.enabled", false);
#else
pref("my.preffable.feature.enabled", true);
#endif
in all.js, which will cause the feature to be disabled automatically if
we are building a Release or Beta branch.
RELEASE_BUILD is currently only available in pref JS files.
It is available on Aurora now, so if you have such a feature you can
land a patch one final time there to ensure it gets preffed off for Beta.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
