This test failed since d240785b on devstack.
The self.request_factory.get() just return a request object, which is
being passed to views.course_about() directly without being processed by
edxmako.middleware. The REQUEST_CONTEXT.request in
https://github.com/edx/edx-platform/blob/d240785b17bdcaeb11e4ef24ee4a3697da26c9b4/common/djangoapps/edxmako/middleware.py#L39
is None, instead of request object, which contains the LANGUAGE_CODE and
other stuff used by the view.

Also cleaned up the use of MakoMiddleware. Using the method in
edxmako.tests module.

Comparing currencies with same case

Ahodges/staff labeling

This reverts commit c94abd27.

This reverts commit 85b3bfe4.

Includes the changes from 897fddba.
Those changes were introduced while resolving a merge
conflict from release back into master.

XCOM-312

Adds the "order" field that was introduced in 0011 to the "models"
dictionary of migrations 0012 and 0013 so South knows that
the field should exist after 0011 is run.

Fix a small typo for credit requirements on the progress page.

Remove unused Ruby gems

Fix 'stuck in publish issue' when deleting a component

Fix hinted login view to be compatible with secondary providers.

Added more descripted release script message

These were only used by rake, and we haven't used rake in a year.

TNL-2665 Prevent Taiwan from being translated

Update LMS student dashboard to use CourseOverview

Disable flaky GroupConfigurationsPage JS test TNL-1475

Revert "Update copy for On Demand Cert Download"

Update copy for On Demand Cert Download

Fix flaky js tests caused by ajax requests TE-970

[LTI Provider] Refactoring to remove the lti_run method

Make the release script use the primary email from people.yaml

Fixed 'play_video' event which was emitting with wrong params.

This change is a follow-up to the chages in PR 8347, which removed the
edX login page from the workflow for a new user. Where previously we
redirected a user to the login page, PR 8347 instead creates a new user
transparently and logs them in.

The initial reason for splitting the LTI view between lti_launch and
lti_run was so that there was a target for the GET request that
followed the login page. Since we no longer use the login page, we
no longer need the second view. We also don't need to store the LTI
parameters in the session any more, since they are not persisting
between calls. This simplifies the view logic significantly.

The other change here is to fetch the LtiConsumer object early in
the view, and pass it to the SignatureValidator and scoring system.
When the views were split, this required multiple DB hits for the
same data; we're now only fetching it once.

ECOM-1651

"play_video" event emitted after seeking forward in a video contains old position