862524 - ship it should compare previous releases' l10n changesets to current l10n changesets

Status: RESOLVED WONTFIX

(Release Engineering :: Applications: Shipit, defect, P3)

Description

[[e-mail] (:bhearsum)]

One of the eyeball checks we do when reviewing releases on ship it is to compare the previous release's l10n changesets to the current release's l10n changesets. Generally we're looking for two things:
1) locales being added or removed
2) platform changes in mobile

These aren't necessarily errors, but they're something that should be noted to the user, I think. This could be calculated server side during a GET to /releases.html and shown on the page somewhere.

The trick is figuring out "previous release"...I don't think there's a way to do that yet.

Comment 1

[Lawrence Mandel [:lmandel] (use needinfo)]

(In reply to Ben Hearsum [:bhearsum] from comment #0)
> One of the eyeball checks we do when reviewing releases on ship it is to
> compare the previous release's l10n changesets to the current release's l10n
> changesets. Generally we're looking for two things:
> 1) locales being added or removed
> 2) platform changes in mobile
> 
> These aren't necessarily errors, but they're something that should be noted
> to the user, I think. This could be calculated server side during a GET to
> /releases.html and shown on the page somewhere.

I think this would be useful.
 
> The trick is figuring out "previous release"...I don't think there's a way
> to do that yet.

Not yet but seems like we might have enough data after bug 826753 is resolved. (Not sure. We still may need to tell ship-it what actually shipped.)

Comment 2

[[e-mail] (:bhearsum)]

Mass component change for ship it bugs.

Comment 3

[Rail Aliiev [:rail]]

We automatically fetch the l10n changesets now. No more milestones! \o/