Does this work with Django 1.8.2 about django-booking HOT 6 CLOSED

@Jzarecta I'm afraid we have never tried. My guts feeling is that this should probably work or at least be very little effort to get it working. I think we just need to rename the migrations folder into south_migrations and then initiate a new migrations folder which uses the core migrations module.

Then we need to document that south users need to specify that their old south-based projects should look for the south_migrations folder and everyone else who wants to upgrade needs to make sure that

1. they update to this latest version and run the migrations
2. now they disable south and switch to core migrations, there will only be one initial migration and they should run it with the --fake flag

@Tyrdall @dkaufhold do you remember if we ever used this in a 1.8 project?

from django-booking.

@mbrochh @dkaufhold I haven't.

from django-booking.

@mbrochh @Tyrdall me neither.
django-libs is ready for 1.8, right? Other than that I'd agree with it only being the migrations that need to be changed.

from django-booking.

Ok sounds good. I think if no one else sends a pull request, I'd like to give the migrations thing a go sometime this week before Sunday.

from django-booking.

@mbrochh Have you tried this in django 1.8? Or, has anyone else tried this in django 1.8 to get it successfully working?

from django-booking.

Works with 0.7.2

from django-booking.