Ned Batchelder 9257f68fd8 The default TIME_ZONE should be UTC ...

In production, we use UTC as the time zone.  DRF 3.7.7 now puts all
times in the currently set timezone where it used to use UTC.  By
setting TIME_ZONE to UTC, we keep the same results we used to get.

In a few places, we had to change the expected test results to be UTC.

2019-06-10 15:27:39 -04:00

..

docs/decisions

Add ADRs for FBE decisions

2019-01-28 13:16:53 -05:00

management

INCR-224: run python-modernize and isort for openedx/features/course_duration/ (#20429)

2019-05-07 08:47:10 -04:00

migrations

INCR-224: run python-modernize and isort for openedx/features/course_duration/ (#20429)

2019-05-07 08:47:10 -04:00

templates/course_duration_limits/edx_ace/expiryreminder/email

REVMI-96: Add a management command to experiment with Access Expiry reminder emails for FBE

2019-03-06 11:44:29 -05:00

tests

The default TIME_ZONE should be UTC

2019-06-10 15:27:39 -04:00

__init__.py

Create shell django app for course duration feature

2018-10-12 16:43:13 -04:00

access.py

INCR-236 (#20502)

2019-05-23 11:53:58 -04:00

admin.py

INCR-236 (#20502)

2019-05-23 11:53:58 -04:00

apps.py

INCR-236 (#20502)

2019-05-23 11:53:58 -04:00

config.py

INCR-236 (#20502)

2019-05-23 11:53:58 -04:00

message_types.py

INCR-236 (#20502)

2019-05-23 11:53:58 -04:00

models.py

INCR-236 (#20502)

2019-05-23 11:53:58 -04:00

resolvers.py

INCR-236 (#20502)

2019-05-23 11:53:58 -04:00

tasks.py

INCR-236 (#20502)

2019-05-23 11:53:58 -04:00