South 0.7.3 released
I've released South 0.7.3.
I've released South 0.7.3.
After a slightly too long hiatus, I've released the second bugfix release of the 0.7 series.
For at least a year now, people have been suggesting to me that South should be in Django core.
The first bugfix release of South is now out, and there's plenty of fixes.
After months of hard work, refactoring, blood, sweat, tears, and improvement, South 0.7 is ready.
It's that time of the year again, when a new South release rears its well-refactored, database-independent head.
In my neverending quest to save the time of those using RDBMSen, South 0.6.2 is released.
South 0.6.1 is now available for public consumption; it fixes quite a few bugs.
It is with great pleasure (and a measurable sense of relief) that I announce the release of South 0.6, a new release bringing quite a few new features, although most of them aren't immediately obvious.
After a long few months, during which I've increased my recommendations to run off trunk, South 0.6 is almost here.
It's about time I posted an update on what's going on with South development, so here it is.
I had a lot of interesting chats with people about South last week at EuroDjangoCon, and several eyebrows have been raised at me both parsing models and then storing their definitions as dicts.
For those interested, the slides from my migrations talk at EuroDjangoCon are up. I believe the videos will be around soon.
I'm pleased to announce the release of South 0.5; this has been a long and exciting release, with many new features...
Work on South has been going full steam ahead lately, with some good results.
After far too many months of quiet feature development and bug fixing, we're happy to finally announce South 0.4, which has a whole host of new features to satiate your every migration need.
The list of new features alone really is quite long; you can see it at http://south.aeracode.org/wiki/ReleaseNotes/0.4, but I'll go through a few of them quickly:
It's been a while since I last talked about South, so it's about time I did a short update, I think. There's been a fair few things going on since last time, which was, err, a long time ago.
Firstly, we now have SQLite support (apart from column renames/alters/deletes; I'll be implementing those with the appropriate workarounds soon). This was one of the features I most wanted to roll in, since SQLite is quite widely used for quick development. SQL Server support is also on the way soon!
Also in the news, TWiD's latest episode has some interesting poll results for schema migrations; of the respondents, over half are using one of the premade tools, and of those about 2/5 are using South - good news for the migration camp overall, and a surprisingly high amount for South, considering I have a limited picture of who's using it.
The world of migrations in Django is definitely warming up now, and with that we're proud to announce the release of South 0.3, the 'intelligent django migrations app', available now from south.aeracode.org.
New in this release are the use of fields rather than dicts for specifying columns in migrations, so migrations now look cleaner, work with all the databases Django supports to a better extent, and even support custom fields.
Also new is dependencies between apps, for those situations where your forum app's Post depends on your accounts app's Profile; South will work out the right way to apply everything so foreign keys don't horribly break.
With the launch of its own site - south.aeracode.org - and Andy McCurdy jumping in to help out, South has been making some good progress. We've made a few backwards incompatable changes, which while annoying will hopefully make things much easier in future.
After the initial release some time last week, and a generally positive reaction, South now has a 0.2 release.
The most important (and only major) change is the addition of MySQL support, so the other section of Django users can finally give it a try. There's also the ability to create all models' migrations at once.
Tired of having to drop tables to re-syncdb your django models? Django-evolution not working, or too magic? Then I have just the solution; my newest project, South; intelligent migrations for Django projects.