Assurance of consistent behavior of migrations
Migrations will run the same way every time and produce consistent results, meaning that what you see in development and staging is exactly what will happen in production - no unexpected surprises.
I think it is a technically correct assertion, but actually the user may have a completely different data on the production machine. Which means the migrations will work the same way, but it won’t necessarily lead to the same result (which is actually the thing some users will expect after they have read such assurance of consistent behavior). For instance, some errors will only occur with specific data (which may be only on the production server).
Change History
(5)
| Triage Stage: |
Unreviewed → Accepted
|
| Owner: |
changed from nobody to mardini
|
| Status: |
new → assigned
|
| Resolution: |
→ fixed
|
| Status: |
assigned → closed
|
I think this is a valid point - the current text is very strong in its assertion, and this may hit some users unexpectedly. I agree we should add a sentence to mention the case you describe.