Define "real". Like I told you, it doesn't bother me.
> Migrations were something that SO many people wanted
You are right - and we had South for it and we used it a lot. Integrating South into Django's core was not a trivial effort, however, but, again, since we already had South, it was not a big issue.
> That is 14 months and $30,000 to get a feature into the framework while already having a tested and battle hardened implementation as a third party module.
IIRC, the 30K were paid to the third party who created South to build a better migration engine it into Django. You can continue to use South for as long as you want. It's just that, starting with 1.7, you'll get migrations built in and South will no longer be required.
I still fail to see why do you think everybody has to be concerned with the problems you find important. If it bothers you so much, then solve it.
edit: corrected the character of the effort