Should we add IgnoreMigration()into the second step migration? #32
Description
The question is about the second step:
Lastly, after the changes above have been deployed, field1 can then safely be removed in the model (plus another makemigrations run)
When we remove a field that was deprecated in the previous release by adding deprecate_field(), should we add IgnoreMigration() into migration where we remove the field in the second step?