Hi Sabine,
Yes, this error is related to 1.7; no, it's not related to migrations. It's related to the App Loading refactor:
The error is caused because you're interacting with Django models before all the models are known to be loaded. If you're starting a completely vanilla Python shell, (i.e., not manage.py shell), then the error has been caused because you haven't called django.setup() - this is a new method required in 1.7 to bootstrap the Django environment.
If you're seeing this error in a manage.py, then there is clearly some sort of complex interaction occurring during the loading of your models; we'll need more details about your setup to be able to diagnose what is going on.
You'll find more details about the new App infrastructure in the docs:
Yours,
Russ Magee %-)