Django 1.6.2 and 1.7a2 released

I clicked, read, nodded in approval and upvoted.. There&#x27;s nothing really to discuss. There are a few new features in 1.7 that people are looking forward to but nothing really controversial.<p>Start a discussion about Python 3, on the other hand, and you&#x27;ll get multi-page comments.

I see they plan to use pyinotify if installed (Linux only).<p><a href="https://docs.djangoproject.com/en/dev/releases/1.7/#management-commands" rel="nofollow">https:&#x2F;&#x2F;docs.djangoproject.com&#x2F;en&#x2F;dev&#x2F;releases&#x2F;1.7&#x2F;#manageme...</a><p>Any reason to stay away from the cross plateforme Watchdog?<p><a href="http://packages.python.org/watchdog/" rel="nofollow">http:&#x2F;&#x2F;packages.python.org&#x2F;watchdog&#x2F;</a>

There is a striking contrast on HN between this release and say, when Node or Rails release a new version. At the one hour point since this was posted and there are no comments.<p>Anybody use Django? Or just not excited about this release? I&#x27;m genuinely curious.

On a related note, Does anyone have any experience with schema migrations in 1.7? Is it similar to South in function and performance? In other words, should I keep using South, or try to learn to use the new implementation? Do I need to be a guinea pig?

I tried Django for the first time last year. I had previously used Drupal&#x2F;Joomla, but hated PHP. Plus Django was much lighter weight - it was easy to build a CMS with it, but also really easy to create something much more minimal.