search

FinalsClub / karmaworld

KarmaNotes.org v3.0
GNU Affero General Public License v3.0
7 stars 6 forks source link

Upgrade Django from 1.5 to 1.6 or 1.7 #380

Open btbonval opened 9 years ago

btbonval commented 9 years ago

1.5 is no longer supported by the Django team.

@yourcelf has experience upgrading from 1.5 to 1.6. It might be wise to push all the way to 1.7 while the pushing is good.

btbonval commented 9 years ago

See also #263

sethwoodworth commented 9 years ago

Jumping to 1.7 involves dropping south and using django's new built-in migrations. That probably isn't a problem, but it is worth knowing this so you update all dev, staging and deployment databases with the latest migrations before the changeover.

On Fri, Jan 9, 2015 at 11:51 AM, Bryan Bonvallet notifications@github.com wrote:

See also #263 https://github.com/FinalsClub/karmaworld/issues/263

— Reply to this email directly or view it on GitHub https://github.com/FinalsClub/karmaworld/issues/380#issuecomment-69362110 .

btbonval commented 9 years ago

Thanks for the heads up @sethwoodworth . @yourcelf made a similar comment, which is why we're still unsure whether to take it all the way to 1.7 or stop at 1.6 for the time being.

Ultimately, those changes will have to get made sometime, unless 1.6 ends up being a long term release.

sethwoodworth commented 9 years ago

I just upgraded an app from 1.5 to 1.6 and it was painless. So long as you run your migrations from south before you upgrade, the upgrade should be kosher. But if you ever want to restore an old db ('meh' imo) it might get a bit hairy. But that should at most ever happen once, if it ever happens at all.

On Fri, Jan 9, 2015 at 2:30 PM, Bryan Bonvallet notifications@github.com wrote:

Thanks for the heads up @sethwoodworth https://github.com/sethwoodworth . @yourcelf https://github.com/yourcelf made a similar comment, which is why we're still unsure whether to take it all the way to 1.7 or stop at 1.6 for the time being.

Ultimately, those changes will have to get made sometime, unless 1.6 ends up being a long term release.

— Reply to this email directly or view it on GitHub https://github.com/FinalsClub/karmaworld/issues/380#issuecomment-69385623 .

AndrewMagliozzi commented 9 years ago

Thanks for the input, Seth.

On Fri, Jan 9, 2015 at 2:32 PM, Seth Woodworth notifications@github.com wrote:

I just upgraded an app from 1.5 to 1.6 and it was painless. So long as you run your migrations from south before you upgrade, the upgrade should be kosher. But if you ever want to restore an old db ('meh' imo) it might get a bit hairy. But that should at most ever happen once, if it ever happens at all.

On Fri, Jan 9, 2015 at 2:30 PM, Bryan Bonvallet notifications@github.com

wrote:

Thanks for the heads up @sethwoodworth https://github.com/sethwoodworth

. @yourcelf https://github.com/yourcelf made a similar comment, which is why we're still unsure whether to take it all the way to 1.7 or stop at 1.6 for the time being.

Ultimately, those changes will have to get made sometime, unless 1.6 ends up being a long term release.

— Reply to this email directly or view it on GitHub < https://github.com/FinalsClub/karmaworld/issues/380#issuecomment-69385623>

.

— Reply to this email directly or view it on GitHub https://github.com/FinalsClub/karmaworld/issues/380#issuecomment-69386008 .

btbonval commented 9 years ago

This is something that might be done in parallel with #426 . Migrating to a new stack could mean a lot of changes to the Heroku environment. Upgrading the version of Django at the same time sounds smart.