Closed harrislapiroff closed 10 years ago
Hah. That's pretty great.
What's up with the hotfix branch that's only merged into 1.0.X (which apparently doesn't contain a bunch of other commits?)
I... looked at that and have no idea. We should clean up the repo too and figure this all out. I just took some NyQuil though, so I'm useless tonight. :p
On Mon, Feb 24, 2014 at 1:30 AM, Stephen Burrows notifications@github.com wrote:
What's up with the hotfix branch that's only merged into 1.0.X (which apparently doesn't contain a bunch of other commits?)
Reply to this email directly or view it on GitHub: https://github.com/littleweaver/django-daguerre/issues/50#issuecomment-35860807
Released 1.0.1 and pushed to pypi. Currently cutting 2.0.0.
2.0.0 release also out now.
2.1.0 release (1.7+ with native migrations) is now out as well.
Wait, 2.1.0 should definitely come with upgrade instructions that specify that if you're upgrading from 1.0 you MUST stop at 2.0.0 in between, with Django 1.6, run south migrations, then upgrade to 1.7 and run migrate. There's no way for people to know otherwise, unless they're us.
8fc04cfaa1c9cf8242368bf48b0da6ea0d396fdc <- acceptable?
Beautiful.
We should really do a new release. The currently available version of Daguerre in PyPI relies on
django.conf.urls.defaults
which does not exist in Django 1.6+.