Pulp

Users should not run django-admin makemigrations because if there is any new migration created, at minimum, it will affect the upgrade in the future.

Cases when django-admin makemigrations produces a new migration:

• users modified code (models)
• there is a bug
  • some migration is not committed
  • existing migrations are not in sync with models, aka incorrect existing migrations

Document that users should never run makemigrations if they are not making some changes on purpose (in this case they are conscious that they will be on their own with the upgrade.), and file a bug if django prompts them to run something like that.