mozilla/fjord — pull request #126 by willkg (2013-07-16 22:00:44+00:00)
Title: L10n deploy fixes 875313

Three things:

1. This is totally fucking awesome. I'm so excited about this.
2. When we initially push this out, we're going to have to spend a lot of time pushing people to fix errors because right now less than half will compile and therefore less than half will ever make it to production.
3. I've tested `./manage.py polint` and `bin/compile-linted-mo.sh`, but can't test the update script changes without being able to deploy. So I'm blocked on bug #894575.

Future thoughts:

1. We might want to distinguish between dev/stage and prod environments and on dev/stage compile everything and only on prod do the selective compile. Then localizers have a system to test against? Right now if there's one bad string, none of it gets compiled anywhere.
2. The only way to discover which .po files were compiled and which have errors is to check the deployment log afterwards. We might want to copy that information to `media/po_status.txt` or something like that so that anyone can discover the latest status of which files were compiled and which weren't. Otherwise not only do things silently fail, but only people who can deploy can find out.
3. This produces a lot of output in the deploy logs. I think I want to tweak dennis so it produces less output. I put in an issue for an --errorsonly flag which will quell maybe 1/3 of it.

Now that I'm thinking about this more, I should implement item 2 now.

feedback?