1302532 - Ensure :IanN has the same (SeaMonkey) permissions in Elmo as Callek

Status: RESOLVED WONTFIX

(Webtools Graveyard :: Elmo, defect)

Description

[Justin Wood (:Callek)]

Hey Pike,

IanN (CC'd) is an en-GB localizer and a SeaMonkey driver. He will be taking over my duties as it relates to l10n&SeaMonkey.

Can you please make sure his Elmo account reflects that power.

(I just tried to walk him through doing a `create milestone` for SeaMonkey and it didn't work)

Comment 1

[Axel Hecht [:Pike]]

Create milestones is not supported anymore, we don't use them for any of our products, and the code in elmo in their support will be removed this week.

Does seamonkey exist in ship-it? 'cause that's where we'll get information from which beta release shipped which version for Firefox.

Comment 2

[Justin Wood (:Callek)]

(In reply to Axel Hecht [:Pike] from comment #1)
> Create milestones is not supported anymore, we don't use them for any of our
> products, and the code in elmo in their support will be removed this week.
> 
> Does seamonkey exist in ship-it? 'cause that's where we'll get information
> from which beta release shipped which version for Firefox.

Unfortunately SeaMonkey doesn't exist in ship-it, at present. Is there some other way (or even a static page/json/repo-checkin/etc) we can provide you for SeaMonkey (thats not shipit) to get this information from us now, or some method on elmo itself?

Comment 3

[Axel Hecht [:Pike]]

I don't think that I'd like to keep around extra code for SeaMonkey, tbh.

I wonder if you can find a way to publish your data in https://product-details.mozilla.org/1.0/l10n/ by side-loading it?

Also, the impact will probably be minor, there's currently only a single view on elmo that uses the milestone data for driver consumption, https://l10n.mozilla.org/shipping/app/locale-changes/sea2.32.

Looking at the data, SeaMonkey has rarely created more than a single milestone per cycle at all, so there wouldn't be a change in exposed data to seamonkey l10n drivers compared to the recent past.

Comment 4

[Justin Wood (:Callek)]

(In reply to Axel Hecht [:Pike] from comment #3)
> I don't think that I'd like to keep around extra code for SeaMonkey, tbh.
> 
> I wonder if you can find a way to publish your data in
> https://product-details.mozilla.org/1.0/l10n/ by side-loading it?
> 
> Also, the impact will probably be minor, there's currently only a single
> view on elmo that uses the milestone data for driver consumption,
> https://l10n.mozilla.org/shipping/app/locale-changes/sea2.32.
> 
> Looking at the data, SeaMonkey has rarely created more than a single
> milestone per cycle at all, so there wouldn't be a change in exposed data to
> seamonkey l10n drivers compared to the recent past.

:Pike, *ahh* ok

So, given that data, assuming the major milestones will stay reflected without a shipit presence, I'm *ok* without build/beta level reflection on this.

If my understanding is accurate we can both move on without worrying about finding any magic way forward.

Comment 5

[Axel Hecht [:Pike]]

Attachment: locale changes old and new

This is how the display changes (right now, changes to that page will happen), once the milestones are lost.

So we'll have information which locales in the 2.32 cycle got updated, but not on which beta. And it won't say something about a final build.

You'll still be able to get the individual revisions of each locale through https://l10n.mozilla.org/shipping/l10n-changesets?av=sea2.32