New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Django #1190

Closed
schakrava opened this Issue Feb 27, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@schakrava
Member

schakrava commented Feb 27, 2016

We are currently running 1.6.2 with South. Update to 1.9.

@schakrava schakrava self-assigned this Feb 27, 2016

@schakrava schakrava added this to the Kilauea Iki milestone Feb 27, 2016

schakrava added a commit to schakrava/rockstor-core that referenced this issue Mar 31, 2016

schakrava added a commit to schakrava/rockstor-core that referenced this issue Mar 31, 2016

schakrava added a commit to schakrava/rockstor-core that referenced this issue Apr 2, 2016

schakrava added a commit to schakrava/rockstor-core that referenced this issue Apr 2, 2016

@schakrava schakrava modified the milestones: Looney Bean, Kilauea Iki Apr 3, 2016

schakrava added a commit to schakrava/rockstor-core that referenced this issue Nov 24, 2016

Update django-pipeline. #1190
As part of updating django, we'll need to update django-pipeline as
well. Splitting it into a separate step and taking it out of the way
makes the next patch less messy.

schakrava added a commit that referenced this issue Nov 24, 2016

schakrava added a commit to schakrava/rockstor-core that referenced this issue Nov 25, 2016

Add new migrations for django 1.8 upgrade. #1190
Move all old/south migrations to south_migrations directory. We'll
delete them soon after successfull upgrade.

Create new native-django initial migrations for both storageadmin and smart_manager.

schakrava added a commit to schakrava/rockstor-core that referenced this issue Nov 25, 2016

schakrava added a commit to schakrava/rockstor-core that referenced this issue Nov 26, 2016

Add new/cleanup migration. #1190
This migration is based on suggested changes by django 1.8, it's not a
functional one. Main reason for adding this now is that it let's us
validate the update process thoroughly.
@schakrava

This comment has been minimized.

Show comment
Hide comment
@schakrava

schakrava Nov 26, 2016

Member

Fixed by #1546 #1545

Member

schakrava commented Nov 26, 2016

Fixed by #1546 #1545

@schakrava schakrava closed this Nov 26, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment