Django 1.7 support about cookiecutter-django HOT 9 CLOSED

Correct me if I'm wrong but the only things that will need changing are:

1. Update requirements.txt to pull down Django 1.7 https://github.com/pydanny/cookiecutter-django/blob/master/%7B%7Bcookiecutter.repo_name%7D%7D/requirements/base.txt
2. The User application uses migrations, we need to update these to use the in-built migrations in Django 1.7 which should be easy as we don't need to provide backwards compatibility (this is a starter template after all). https://github.com/pydanny/cookiecutter-django/tree/master/%7B%7Bcookiecutter.repo_name%7D%7D/%7B%7Bcookiecutter.repo_name%7D%7D/users/migrations

It's probably worth checking through the release notes though.

from cookiecutter-django.

South will have to be removed. We'll also need to confirm that django-avatar works. Otherwise I think that's it. I won't have time to work on this for a few days, but pull requests are welcome. 😉

from cookiecutter-django.

At first sight it looks like those are the ones. I'll have a better look at the change logs later.

Are you planning on tagging the current commit as "Django 1.6.6" and jumping directly to Django 1.7?
Or creating different branches?

Think there will still be devs interested in having Django 1.6 supported as well, due to some third party apps probably not supporting Django 1.7 yet. Would probably recommend tagging if possible.

from cookiecutter-django.

I think creating both different branches and tags is a brilliant, brilliant idea. I'll do that right now. If I get the chance later I'll note this in the documentation.

from cookiecutter-django.

@pydanny awesome! :D

btw I noticed this pull request #128, is Django 1.7 support ready to be tested?

from cookiecutter-django.

Yes, please help test the 1.7 support!

from cookiecutter-django.

+1

from cookiecutter-django.

Closed?

from cookiecutter-django.

Opps, I forgot to close this issue.
@matheusjardimb yes closed.
Thanks for telling.

from cookiecutter-django.