Skip to content
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

Add Django Migrations #164

Closed
wahuneke opened this issue Jul 24, 2015 · 1 comment
Closed

Add Django Migrations #164

wahuneke opened this issue Jul 24, 2015 · 1 comment
Milestone

Comments

@wahuneke
Copy link

Sorry, this is a really obvious one but I couldn't find any documentation or mention anywhere, even in issues, about migrations and south.

So this is really more of a question: Why are there no migrations in this project? Will they be introduced at some point? Are you waiting to use Django native migrations (introduced in 1.7)? Maybe just waiting until you can declare 1.7 as minimum supported version?

It seems to me (and I'm sure to you too) that lack of migrations may be really holding back growth and development in the django-stripe-payments app.

I'm planning on adding (South-style) migrations in my fork, but it would be nice to know your plan so I'll be able to push my work upstream some day.

Thanks!

@paltman paltman added this to the 2.0 milestone Nov 12, 2015
@paltman paltman changed the title Migrations support (what's the plan?) Add Django Migrations Nov 12, 2015
@paltman
Copy link
Member

paltman commented Nov 12, 2015

@wahuneke Yes, we were waiting on all Pinax apps until minimum supported version of Django became 1.7 which is now is. I have marked this issue as inclusion for the 2.0 Milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants