…. [bug 662476, bug 662474]
…y in the admin. This gets rid of the menu which was causing crazy slowness while also hiding the little magnifying glass which doesn't work without Revision also being an admin-registered type.
Also add a one-time management command to fix existing weekly vote counts.
…age. [bug 663808]
[bug 661853, bug 661847]
…mere approval. This involves changes to the UI, to models, and to the l10n dashboards.
… so) on deletion of a revision. Also, return '' instead of None from Document.content_parsed when there is no current revision. Hooray for consistently typed return values.
…om bug 662747. ...namely, that a revision is made "ready" at review time, not when created.
…rmission to protect it. [bug 662747]
…dy-for-l10n bit. * In translation and translation-review views, offer to translate the latest ready-for-l10n revision, not the latest approved one. (More specifically, replace the old obsession with the current-or-latest revision with one about the latest-localizable-or-latest revision.) Kill the old tests for now; most of them will be back to test localizable_or_latest_revision(). * Change semantics of Revision.based_on to take is_ready_for_localization into account. * Default is_ready_for_localization to False as per conversation with Michael Verdi. * Have translated_revision() default is_ready_for_localization to True. This maintains the same semantic as before the field existed, which should keep most of the tests happy.
In the spirit of fat models and reducing opportunities to screw up, move on-delete code from the view into the Revision model.