Skip to content
Commits on Jun 15, 2011
  1. @tgavankar
Commits on Jun 10, 2011
  1. @erikrose

    [bug 639806] Add the concept of a doc being "ready for l10n", beyond …

    …mere approval.
    This involves changes to the UI, to models, and to the l10n dashboards.
    erikrose committed Jun 9, 2011
  2. @erikrose
  3. @erikrose
  4. @erikrose

    Make new content of Document.html correct (or at least more obviously…

    … 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.
    erikrose committed Jun 8, 2011
  5. @erikrose

    Bring test_ready_for_l10n_updates_doc up to date with spec changes fr…

    …om bug 662747.
    ...namely, that a revision is made "ready" at review time, not when created.
    erikrose committed Jun 9, 2011
  6. @rlr @erikrose

    Moved ready for localization checkbox to approve modal and added a pe…

    …rmission to protect it. [bug 662747]
    rlr committed with erikrose Jun 8, 2011
  7. @erikrose
  8. @erikrose

    Revise translation-related views and based_on model semantics for rea…

    …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.
    erikrose committed Jun 7, 2011
  9. @erikrose

    Add model code to keep document.latest_localizable_revision up to date.

    In the spirit of fat models and reducing opportunities to screw up, move on-delete code from the view into the Revision model.
    erikrose committed Jun 6, 2011
  10. @erikrose

    Update L10n Dash to take ready-for-localization into account.

    Add denormalized latest_localizable_revision field for comprehensibility (and a bonus of speed).
    erikrose committed Jun 6, 2011
  11. @erikrose
Commits on Jun 9, 2011
  1. @tgavankar
  2. @tgavankar
  3. @erikrose
Commits on Jun 8, 2011
  1. @erikrose
  2. Tolerate missing Redis servers. [bug 662942]

    James Socol committed Jun 8, 2011
  3. @erikrose

    Docstring typo

    erikrose committed Jun 6, 2011
  4. @tgavankar
  5. @tgavankar
  6. @rlr
  7. Fix gettext context.

    James Socol committed Jun 8, 2011
Commits on Jun 7, 2011
  1. @rlr
  2. Parse wiki content in private messages. [bug 658401]

    James Socol committed Jun 7, 2011
  3. @rlr

    Added admin edit link to user profiles (only show to staff users with…

    … the change_profile pperm). [bug 658557]
    rlr committed Jun 6, 2011
  4. @rlr
  5. @rlr
Commits on Jun 6, 2011
  1. @tgavankar
  2. @rlr

    Added default field to the browser versions namedtuple. Now default i…

    …s independent of order \o/. [bug 661885]
    rlr committed Jun 3, 2011
  3. @rlr

    Fix for showfor default fallbacks. Now we apply the new logic to the …

    …default browsers. [bug 661862]
    rlr committed Jun 3, 2011
  4. @tgavankar
  5. Use the new MultiDB strategy for indicating writes.

    * explicitly indicates when it did a DB write.
    * The new PinningRouterMiddleware notices this and sets the cookie if
    James Socol committed May 18, 2011
  6. Add Redis backends to /services/monitor [bug 659518]

    James Socol committed Jun 6, 2011
Commits on Jun 3, 2011
  1. Drop Question.status and Question.confirmation_id [bug 661630]

    Remove the old columns for confirming questions, an old view, and update
    search and a couple of tests.
    James Socol committed Jun 3, 2011
Something went wrong with that request. Please try again.