Closed Bug 850495 Opened 12 years ago Closed 12 years ago

Set up mirroring of b2g v1.1 branches to git.m.o

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: catlee, Unassigned)

References

Details

Attachments

(2 files)

No description provided.
Blocks: 850481
Component: Release Engineering: Automation (General) → Release Engineering: Developer Tools
QA Contact: catlee → hwine
Blocks: 850485
No longer depends on: 850485
Depends on: 850482
Assignee: nobody → hwine
Status: NEW → ASSIGNED
Attachment #735404 - Flags: review+
Attachment #735404 - Flags: checked-in+
Comment on attachment 735404 [details] [diff] [review] config changes for gaia v1.1.0 support deployed in production - errors will appear in log until v1.1.0 is actually created in the upstream repo. No email alerts will be reported due to those errors.
Attachment #735427 - Flags: review?(catlee)
Comment on attachment 735427 [details] [diff] [review] gecko 1.1.0 support Looks good. Do we need to wait until we're closer to our actual branch date before we start pushing gecko out to git? What happens if we need to reset the repo for some reason?
Attachment #735427 - Flags: review?(catlee) → review+
If we're at all concerned with a reset of the repo, we should hold off on landing this. I don't want to run into another reset issue. Holler when you want it landed & deployed.
Assignee: hwine → nobody
We're not going to be needing separate v1.1.0 branch mechanics.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
Product: mozilla.org → Release Engineering
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: