On Aug 16, 2013, at 5:01 PM, Mark Finkle <[email protected]> wrote:
>
>
> On Aug 16, 2013, at 4:37 PM, Mark Finkle <[email protected]> wrote:
>
> When do we uplift?
>
> How about Weeklyish. Not so often that there's overly-much process, but
> frequently enough that we avoid annoying merge issues and don't drift too far
> from m-c.
> Pulling from past experience, I would suggest waiting until we are done to
> push elm back into mozilla-central. The elm branch will have it's own
> Nightlies. We do not need to rush anything into mozilla-central and worry
> about using preferences or flags to control the new code.
>
> Wait. For migration purposes, don't we need to keep new and old code fully
> functional? That was my belief when I authored this:
> https://bugzilla.mozilla.org/show_bug.cgi?id=906011
>
> We can use preferences/flags, if needed, in the final shippable form, but we
> shouldn't use them to protect half-finished code from the rest of the code.
> That's the purpose of using a branch.
So to be landable in m-c, the pref is a requirement. I guess you're just
saying that it's easier to add the pref at the end in the branch right before
landing?
Is this correct? If so, it blows up my iterative testing by jbonacci to ensure
no mainline regression thought.
lloyd
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
