Project

Profile

Help

Task #6703

Document that users should not run makemigrations but file a bug instead

Added by ttereshc 12 months ago. Updated about 1 month ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation
Sprint:
Quarter:

Description

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.

History

#1 Updated by ttereshc 8 months ago

  • Project changed from RPM Support to Pulp

#2 Updated by ttereshc 5 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ttereshc
  • Sprint set to Sprint 86

#3 Updated by rchan 5 months ago

  • Sprint changed from Sprint 86 to Sprint 87

#4 Updated by rchan 4 months ago

  • Sprint changed from Sprint 87 to Sprint 88

#5 Updated by rchan 3 months ago

  • Sprint changed from Sprint 88 to Sprint 89

#6 Updated by rchan 3 months ago

  • Sprint changed from Sprint 89 to Sprint 90

#7 Updated by rchan 2 months ago

  • Sprint changed from Sprint 90 to Sprint 91

#8 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 91 to Sprint 92

#9 Updated by ttereshc about 1 month ago

  • Status changed from ASSIGNED to NEW
  • Assignee deleted (ttereshc)
  • Sprint deleted (Sprint 92)

Never got to it. Not a priority at the moment.

Please register to edit this issue

Also available in: Atom PDF