Process for evaluating features after a merge to Aurora

Margaret Leibovic margaret.leibovic at
Thu May 29 14:26:45 PDT 2014

And in case you don't know, we keep track of the features we're working on
in our roadmap wiki page [1], so we shouldn't be surprised by the things
that end up being merged into Aurora, whether they're ready or not. If
you're working on a feature that's more than a small bug fix, you should
make sure it's listed in the roadmap, so that it's easier for everyone to
track the big changes happening in our product. Jenn maintains this wiki
page, so you should talk to her if you notice something that's missing.



On Thu, May 29, 2014 at 1:31 PM, Mark Finkle <mfinkle at> wrote:

> Hi All,
> Just an FYI that the Firefox for Android team will be getting a bit more
> strict with evaluating the readiness of features after a merge to Aurora.
> In general, we've found that we do too much "catch-up" work on Aurora, and
> sometimes Beta, as we hurry to get features fixed and polish as they ride
> the trains out to release. It causes some inefficiencies and stress, as
> well as the potential for lower quality releases.
> Therefore, we intend to start being a bit more strict with features that
> merge to Aurora. If a feature is not deemed ready - either for UX, polish
> or stability reason - we'll back it out or turn it off in Aurora. We'll be
> meeting early the week of a merge to discuss feature readiness.
> We did not want this action to be seen as anything other than making sure
> Firefox for Android is the best it can be. Getting a feature backed out of
> Aurora is not the worst thing that can happen. Shipping a poorly
> functioning feature is much worse.
> Thanks,
> Finkle
> _______________________________________________
> mobile-firefox-dev mailing list
> mobile-firefox-dev at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the mobile-firefox-dev mailing list