Closed Bug 1225518 Opened 4 years ago Closed 4 years ago

Create new branch for B2G stabilization ("OTA branch")

Categories

(Release Engineering :: General, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: catlee, Assigned: hwine)

References

Details

(Keywords: meta, Whiteboard: [tracker])

We need to set up a new branch in buildbot, TC, hg, github, etc. to support a new initiative for B2G. AIUI their objective is to have a branch to stabilize code from mozilla-central/master, from which OTA updates for dogfooders will be produced.

Jean, Mahe, please correct me if I'm wrong!

As this will be use to produce builds to release to users, I can think of a few options for what to call this repo:

releases/b2g-ota
releases/b2g-ota-stabilization
releases/b2g-stabilzation
releases/b2g-foxfood

This will also require new branches in gaia and b2g-manifests. We'll need b2gbumper support as well. I don't think we'll need separate l10n support.
Thanks Chris. Summary is right. 

We had a vote in our weekly meeting on its name. 

Let's call it b2g-ota
Spoke with Jean and Mahe, and we agreed on releases/b2g-updates
Assignee: nobody → hwine
If its still not too late, Fabrice prefers it being b2g-OTA 

Am inclined for b2g-OTA too..
Final configuration plan (from several side conversations):
 - branch to be 'b2g-ota'
 - branch point will be gaia master & gecko mozilla-central
 - gecko branches will be established as soon as practical

Items not part of this plan:
 - any requests for associated Bugzilla flags, if needed.
 - any gaia l10n branching
Keywords: meta
Whiteboard: [tracker]
Status: NEW → ASSIGNED
Depends on: 1227319
AIUI, this branch will not be officially released to partners. If that is the case, we should not include the b2g-ota branch in either the official git.mozilla.org releases/gecko.git or releases/gaia.git repositories. (The new gecko branch will be in gecko-dev.git on both github and git.mozilla.org.)

:mahe ni to confirm that is correct.
Flags: needinfo?(mpotharaju)
That is right Hal. We do not make this branch available to partners.
Flags: needinfo?(mpotharaju)
Depends on: 1227331
Depends on: 1227332
Depends on: 1227333
Depends on: 1227340
Depends on: 1227346
Depends on: 1227349
Depends on: 1227350
Depends on: 1227352
Depends on: 1227355
Depends on: 1229392
Depends on: 1229415
Depends on: 1229418
Depends on: 1229247
All work done. Hopefully, this dependency tree will be useful for next time.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
How often are we pushing to this channel?  As far as I see the last push is 12/2.  Are we automating the pushes?  Or are these going to be manual pushes?
Flags: needinfo?(mpotharaju)
Flags: needinfo?(hwine)
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #9)
> How often are we pushing to this channel?  As far as I see the last push is
> 12/2.  Are we automating the pushes?  Or are these going to be manual pushes?

We are trying for a weekly push to this channel.  We didn't push an update last week due to Mozlando so we will try for one this week.  The push will be manual in the first month (or so) to see how it goes then we will transition to an automatic system.
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #9)
> How often are we pushing to this channel?  As far as I see the last push is
> 12/2.  Are we automating the pushes?  Or are these going to be manual pushes?

All pushes between gecko branches are done manually. For desktop/mobile, this work is handled by the sheriffs, I have no idea if they are supporting b2g-ota.

In particular, since this is a stabilization branch, I would expect that only certain commits will be uplifted to b2g-ota, based on some bugzilla flags. At least that is the process for desktop/mobile train branches.
Flags: needinfo?(hwine)
Flags: needinfo?(mpotharaju)
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.