Upgrade to Django 1.8
Django 1.7 has now been released. South is now no longer required, and a new version of South has been released to allow for dual running of the two schemes. However, it breaks how OpenREM is currently setup.
Therefore I need to fix OpenREM for 1.7 installs, probably make 1.7 a minimum requirement in the setup_tools config, and document the procedure for upgrading existing South migrated installs.
Comments (15)
-
reporter -
reporter - changed milestone to 0.6.0
Issue largely resolved by database migration in place for 0.5.1 - suggest Django 1.7 should be a target for 0.6, or maybe 0.5.2?
Need to make sure that a/ it works and b/ we deal properly with existing database migrations.
-
reporter - changed status to open
-
reporter Tasks for 1.7 upgrade:
- Remove
south
fromINSTALLED_APPS
inopenremproject/settings.py
- Add
TEST_RUNNER = 'django.test.runner.DiscoverRunner'
toopenremproject/settings.py
- Add instructions for removing all the existing migration files and running the new commands as per https://docs.djangoproject.com/en/1.7/topics/migrations/#upgrading-from-south
- Remove
-
reporter @dplatten What do you think about upgrading to 1.7 as part of 0.6.0? I think to keep things simple we'd have to insist that everyone upgrades with us.
-
Hi @edmcdonagh. I don't see why not.
-
reporter - changed title to Upgrade to Django 1.7
-
reporter - changed milestone to Future
Not necessary for 0.6.0 - pushed out to next release
-
Changed Django requirements to >=1.8; removed south. References issue
#241and#118.→ <<cset 7c35e56573e2>>
-
Combined datetime and median migrations into one file. Needs testing. References issue
#241and#118.→ <<cset 05776b94a13a>>
-
reporter Changed Django requirements to >=1.8; removed south. References issue
#241and#118.→ <<cset 7c35e56573e2>>
-
reporter Combined datetime and median migrations into one file. Needs testing. References issue
#241and#118.→ <<cset 05776b94a13a>>
-
reporter - marked as enhancement
- changed milestone to 0.7.0
- changed title to Upgrade to Django 1.8
-
reporter - changed status to resolved
This task has largely been carried out by @dplatten
-
reporter -
assigned issue to
-
assigned issue to
- Log in to comment
Fixed for version 0.4.3 by changing the requirements to be django==1.6.
Changed Milestone to Future, and downgraded from Blocker.