When we do a deployment, we have a script that runs and looks at each .po file, lints it and if there are no errors, then it compiles the .po file to a .mo file. This is how new translations make it to our production environment. When there are errors, the errors are logged in a postatus.txt file. For example, this is the url for the one in production: https://support.mozilla.org/media/postatus.txt There's a PR for adding a cron job to tell people whether there are currently errors in the postatus file. However, taking those errors and converting them to bugs so someone can go fix them is a pain in the ass. This bug covers writing up a system like my django security bug system that takes most of the work out of that process.
Grabbing this one. I'll try to do it some time this week. Plus I'll probably build something similar for Input while I'm at it.
Assignee: nobody → willkg
Code is here: https://github.com/willkg/postatus/ Webapp is hosted here: http://postatus.paas.allizom.org/ I intentionally made it pretty minimal. It doesn't keep track of bugs written. When you get to the Bugzilla form, if you add a " " to the summary, it'll check to see if there are already existing duplicates. Anyhow, that covers this bug. If there are pain points, we can write up issues in the github issue tracker and fix stuff there.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
This is fantastic! Thanks so much, Will!
You need to log in before you can comment on or make changes to this bug.