On 4/18/13 1:03 PM, Lukas Blakk wrote:
Hello,
I'm following up on an action from our Firefox 20 Post-Mortem where it was
discussed that it would be helpful to have a way to pref on a set of features
that want to be in early Beta builds to garner feedback and audience reach but
should not ship since they are not ready for public consumption.
Briefly reaching out on #developers identified that we could use a
pre-processing flag in mozconfigs for early betas, something like #ifdef
EARLY_BETA_ONLY_FEATURE in which case it seems to me the actions needed would
be:
* Create and publicize to engineering & product teams the location for listing
feature prefs that need enabling in early beta, but should not ship
* Create the EARLY_BETA_ONLY_FEATURE flag and make sure it enables those prefs
accordingly until we no longer include them in later beta mozconfigs
* Releng automation to switch/edit mozconfigs for earlier betas to check for
this flag
Thoughts? Feedback? People willing to take on any of these items? I'll file
bugs on them soon once we've hashed out the best way to do this.
I think this is a good idea. I've wanted it for a while as well. I've
even already filed a build config bug to support it:
https://bugzilla.mozilla.org/show_bug.cgi?id=853071.
What we don't have are specific and common use cases that need to be
supported. I anticipate that info will be provided shortly :)
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
