1280730 - [mobile] read maemo-locale to control multi-locale build instead of l10n-changesets.json

Status: RESOLVED DUPLICATE of bug 1339706

(Release Engineering :: Release Automation, defect, P2)

Description

[Axel Hecht [:Pike]]

Talked about this with Rail in London, getting a bug on file to investigate and track.

The l10n-changesets.json from the l10n dashboard creates that data by locally reading maemo-locales.

Let's simplify the data-exchange between l10n and ship-it, and have release automation read from maemo-locales directly.

Also has the benefit that it uses the version that's in the build, and not the version that's current when downloading for ship-it. Not that that's ever been a problem, or maemo-locales was fast-changing. Just sanity.

Comment 2

[Justin Wood (:Callek)]

:Pike, so to ask, whats the correlation between maemo-locales and shipped-locales, is it essentially the same.

l10n-changesets.json aiui is basically the same as the l10n-changesets file that the dashboard gives for desktop, only in json format, or is there more to it than that.

Comment 3

[Axel Hecht [:Pike]]

The gist of it is this:

When getting the l10n-changesets.json, we pass in maemo-locales to https://github.com/mozilla/elmo/blob/d2771ffad6f946bd0d580a870b3f203162e656a5/apps/shipping/views/milestone.py#L162, which ends up adding an extra platform for the multi-locale android build to all locales that are in maemo-locales.

This bug is about moving this into the releng automation, and to read maemo-locales from the revision that the multi-locale build is from.

If you look at https://l10n.mozilla.org/shipping/json-changesets?ms=fennec47_beta_b1&platforms=android&multi_android-multilocale_repo=releases%2Fmozilla-beta&multi_android-multilocale_rev=default&multi_android-multilocale_path=mobile%2Fandroid%2Flocales%2Fmaemo-locales, you see data like

  "an": {
    "revision": "fe436c75f71d",
    "platforms": ["android", "android-multilocale"]
  },
  "ar": {
    "revision": "9c4b301989ca",
    "platforms": ["android"]
  },
  "as": {
    "revision": "866666bf57f0",
    "platforms": ["android", "android-multilocale"]
  },
  "az": {
    "revision": "6e5058d71a7a",
    "platforms": ["android", "android-multilocale"]
  },

which means that an, as, az are in the multi-locale build, while `ar` is not.

Comment 4

[Francesco Lodolo [:flod]]

(In reply to Justin Wood (:Callek) from comment #2)
> :Pike, so to ask, whats the correlation between maemo-locales and
> shipped-locales, is it essentially the same.

Also:
mobile/maemo-locales -> Android multi-locale build
mobile/all-locales -> Android single-locale builds

IIRC shipped-locales is used in /browser to determine Beta and Release desktop build, while all-locales is for all builds. Locales shipping in Android and Desktop are quite different.

Comment 5

[Axel Hecht [:Pike]]

Rail, Aki, this bug is dealt with as part of how we fix bug 1339706, the in-tree revisions, right?

Not sure which resolution would be the most appropriate one?

Comment 6

[Aki Sasaki (not active)]

I believe I fixed this in bug 1339706: the bumper reads from maemo-locales, so maemo-locales is now the source of truth for multilocale.