Imagine the following situation:
- Version 1.27 is on the test database
- Version 1.28 got an upgrade script functionality, assigned to ug_after_1_27_to_1_28
- This works perfect and I will create version 1.29 after upgrade.
- After developing and testing version 1.29 I want to deploy 1.29 to the production
- Production is version 1.27, so in the SF I will put 1.27 as previous project version.
- When upgrading from 1.27 → 1.29 I will loose the upgrade script ug_after_1_27_to_1_28
I can imagine that this works the same with branching and merging.
Ususally I will attach these upgrade functionality to ug_after_always to prevent this situation, but then I have to cleanup upgrade scripts after a while.
It would be nice if we can prevent this and the SF would recognise that between 127 and 1.29 there is an upgrade script that needs execution.
