Sorry if this wasn't communicated enough. We shared the plan on an earlier email thread and presented in 2.6 kickoff meeting.
Here is the process involved : The flow will be: 1. Create the OTA branch - gecko and gaia 2. We uplift patches to this branch. Only the ones that fixes smoke test / foxfooder blockers 3. OTA update is launched once the branch passes all the smoke tests / foxfooder tests 4. We update the OTA branch with current master content and back to #2 So, this is going to be a close copy of Master. Yes, strings will be the same on Master and the OTA branch. In terms of frequency - Master will be copied to OTA once we have ship an update. It's not on any regular cadence, but we want to keep the time interval short. For more questions, please email or ping. On Wed, Nov 18, 2015 at 10:25 AM, Francesco Lodolo [:flod] <[email protected]> wrote: > Il 18/11/15 19:18, Mahendranadh Potharaju ha scritto: > > *Branch* > Release Engineering is now working to set up a new branch called *b2g-ota*. > This branch will be used to provide updates to foxfooders. > > Hi, > I haven't seen any details yet on what is going to be in b2g-ota compared > to master. > > My understanding is that the target of b2g-ota is to stabilize master: > would it be safe to assume that strings will be the same on both branches? > How often are master and b2g-ota going to be synced? > > Francesco > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > > -- Mahendra Potharaju
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
