Closed Bug 924575 Opened 8 years ago Closed 8 years ago

switch v1.1x builds to use new gaia-l10n repos

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(blocking-b2g:leo+, b2g18 fixed, b2g-v1.1hd fixed, b2g-v1.2 unaffected)

RESOLVED FIXED
blocking-b2g leo+
Tracking Status
b2g18 --- fixed
b2g-v1.1hd --- fixed
b2g-v1.2 --- unaffected

People

(Reporter: aki, Assigned: aki)

References

Details

Attachments

(3 files)

No description provided.
Attached patch 1.1_l10n_configsSplinter Review
patch 1 of 3, i think
Assignee: nobody → aki
Attachment #814514 - Flags: review?(hwine)
Attached patch b2g18Splinter Review
Attachment #814521 - Flags: review?(hwine)
Attached patch 1.1hdSplinter Review
Attachment #814522 - Flags: review?(hwine)
Comment on attachment 814514 [details] [diff] [review]
1.1_l10n_configs

Review of attachment 814514 [details] [diff] [review]:
-----------------------------------------------------------------

lgtm
Attachment #814514 - Flags: review?(hwine) → review+
Comment on attachment 814521 [details] [diff] [review]
b2g18

Review of attachment 814521 [details] [diff] [review]:
-----------------------------------------------------------------

lgtm
Attachment #814521 - Flags: review?(hwine) → review+
Attachment #814522 - Flags: review?(hwine) → review+
blocking-b2g: --- → leo?
Alex, are you doing leo noms?
in production
Blocks: 918320
blocking-b2g: leo? → leo+
I'd expect to see something here that switches git-based builds from the master branch over to the v1.1 branch. Aki?
(In reply to Axel Hecht [:Pike] from comment #9)
> I'd expect to see something here that switches git-based builds from the
> master branch over to the v1.1 branch. Aki?

That's the second two patches.  Since there is only a single gaia repo per locale on git.m.o, there's no need to switch the git gaia repo.
Not til bug 852238 is resolved, no.
I think we're done here.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
For the future, identical changes that affect b2g18/v1.1hd should just be handled via merges instead of double-landing.
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.