967282 - vcs-sync: gecko l10n is only pushing the mozilla-beta branch

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Aki Sasaki (not active)]

No complaints yet.
We may wait until we migrate from legacy unless there are external reasons to do this earlier.

Comment 1

[Aki Sasaki (not active)]

Worse: we're also pushing the 1.3 branch on certain repos, but that may still be pointing at l10n-central.

We're going to have to do something serious with the gecko l10n repos, potentially a non-ffwd push or deletion.

Comment 2

[Aki Sasaki (not active)]

I think the easiest solution here is to delete all git.m.o gecko l10n repos when we're ready to cut over to new vcs-sync.

Comment 3

[Axel Hecht [:Pike]]

I'm getting questions about gecko l10n for 1.3T in bug 981160, and I guess the real answer is blocked on this bug. I bet that means something for timing, but I have no idea what.

Comment 4

[Axel Hecht [:Pike]]

PS: for 1.3, I think the best gecko content is from the FIREFOX_28_0_RELEASE tag on the mozilla-release repos, actually.

Comment 5

[Aki Sasaki (not active)]

(In reply to Axel Hecht [:Pike] from comment #4)
> PS: for 1.3, I think the best gecko content is from the FIREFOX_28_0_RELEASE
> tag on the mozilla-release repos, actually.

Is that actually different from the mozilla-beta gecko l10n repos?

Comment 6

[Axel Hecht [:Pike]]

Yes, in that the release tag isn't in the beta repos. The tagged changeset is there, though.

Comment 7

[Pete Moore [:pmoore][:pete]]

I think this is resolved now, since we migrated gecko and gaia l10n over to modern vcs sync last year.