Skip to content

Conversation

timgraham
Copy link
Member

(testing)

@jezdez
Copy link
Contributor

jezdez commented Oct 8, 2014

Oh, can we hold off on this one till the redesign is merged? I would guess till end of October.

@timgraham
Copy link
Member Author

Yes, we are still waiting for James to make a decision on the fate of django-registration (presumably choosing a new maintainer).

@jezdez
Copy link
Contributor

jezdez commented Oct 8, 2014

@timgraham Okay, I could port over the code to django-allauth if needed, I recently did that for djangosnippets.org

@timgraham
Copy link
Member Author

@jezdez I found django-registration-redux which seems to be a maintained fork of django-registration which should work for now. How is the new site coming along? Should we still hold off on this? Not sure how the new design will integration with this code? If we can move forward, I think it's ready for merge, but I'd do a little more testing before pushing it live.

@timgraham timgraham force-pushed the django1.7 branch 4 times, most recently from 843794f to df2c281 Compare November 15, 2014 16:48
-Replaced south migrations with built-in migrations.
-Updated to use django-registration-redux.
@timgraham timgraham merged commit 002f83d into master Nov 20, 2014
@timgraham timgraham deleted the django1.7 branch November 20, 2014 12:33
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

Successfully merging this pull request may close these issues.

2 participants