Component: Release Engineering: Automation (General) → Release Engineering: Developer Tools
QA Contact: catlee → hwine
Created attachment 735404 [details] [diff] [review] config changes for gaia v1.1.0 support http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/670ec75d09af automation generated config
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.
Created attachment 735427 [details] [diff] [review] gecko 1.1.0 support
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.
We're not going to be needing separate v1.1.0 branch mechanics.
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
Product: mozilla.org → Release Engineering
Component: Tools → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.