There will need to be work across multiple teams in order to facilitate Release Engineering submitting created language packs to AMO for signing, and pushing the resulting packs to archive.m.o. Currently releng builds language packs and puts them up on archive.m.o then a human (via script) downloads them and signs them against AMO and lists them on AMO. This work is to cut out middle men and the release delays in language packs being available on AMO. Not in scope: Nightly language pack signing, -- While possible to come out of this as a "minor extra work" its not explicitly a goal. In Scope: Having signed language packs ready for ESR60. Timeline: Likely to miss Gecko 60 beta, and could require relatively large uplifts.
If this is something planned and must for 60, I think it makes sense to track it as a blocker for 60 so we review the timeline/readiness regularly.
Where can I read more about why this must make 60?
(In reply to Julien Cristau [:jcristau] from comment #2) > Where can I read more about why this must make 60? One of the drivers was https://bugzilla.mozilla.org/show_bug.cgi?id=1388143 but there is also https://bugzilla.mozilla.org/show_bug.cgi?id=1197876
We're getting there, but enforcing signed langpacks won't happen until 61 and 60.1esr, so dropping the blocking flag for 60.0.
Component: General → Release Automation: Other
QA Contact: catlee
What's the status for 61+ here?
for 61+ we sign and upload signed copies of language packs, I'm not certain if the inquiry was also about "we require signing" though, so I'm sending off to :aswan to confirm that side of the project "just in case"
Flags: needinfo?(bugspam.Callek) → needinfo?(aswan)
In bug 1454141 we made it so signed langpacks are required by default. The requirement cannot be disabled on release and beta, but it can be disabled on all other channels. That bug landed in 61 and was uplifted to ESR 60.1. If I misunderstood the question, apologies and please re-needinfo me.
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.