Closed Bug 1229617 Opened 9 years ago Closed 8 years ago

Determine proper action for b2g-ota branch

Categories

(Release Engineering :: Release Requests, defect)

Product:
Release Engineering
Component:
Release Requests
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: hwine, Unassigned)

References

Details

On Dec 14, when m-c becomes gecko 46, a decision needs to be made about how b2g-ota branch will be handled:
 - will it stay with Gecko 45? or
 - will it stay on default and move to Gecko 46?

There are various files that contain pointers to:
 - gecko version
 - gaia version
 - gecko l10n repos
 - gaia l10n repos

Within:
 - buildbot-configs repo
 - mozharness repo (b2g_bumper)
 - vcs-sync

which need to be adjusted in a coordinated fashion.
ni: mahe for decision
Flags: needinfo?(mpotharaju)
It will move on to Gecko 46. OTA branch runs parallel to m-c.
Flags: needinfo?(mpotharaju)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.