Closed Bug 815142 Opened 12 years ago Closed 12 years ago

we need a mozilla-b2g18 tree (for 12/10)

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Type:
defect

Tracking

(blocking-basecamp:+, b2g18 fixed)

Status:
RESOLVED FIXED
Milestone:
B2G C2 (20nov-10dec)
Project Flags:
blocking-basecamp +
Tracking Flags:
Tracking Status
b2g18 --- fixed

People

(Reporter: akeybl, Assigned: hwine)

References

Details

For 12/10, we'll need a mozilla-b2g18 tree created and synced to mozilla-beta. This request may need to be filled earlier if a required change with significant risk to desktop/android needs to land. In that scenario, our understanding is that tree setup may take about a day.
blocking-kilimanjaro: --- → +
Priority: -- → P2
Target Milestone: --- → B2G C2 (20nov-10dec)
I think we should go ahead and set-up the mechanics of this as soon as we can. That is, clone the repo, set up builders, etc. Then we just need to do a final sync when you're ready to use it.
Component: Release Engineering → Release Engineering: Automation (General)
QA Contact: catlee
Blocks: 815185
Note that the actual cutover needs to be coordinated with the b2g git repos as well. I've opened bug 815185 for that.
starting preparations
Assignee: nobody → hwine
Status: NEW → ASSIGNED
Depends on: 816366
blocking-basecamp: --- → +
blocking-kilimanjaro: + → ---
Depends on: 816766
Depends on: 816775
Depends on: 816797
Depends on: 818378
Depends on: 819411
I believe this is resolved now! \o/
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [status-b2g18:fixed]
status-b2g18: --- → fixed
Whiteboard: [status-b2g18:fixed]
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.