Re: ALM : How to not include time settings in migration
The time settings are considered structural to the model (except now current time) meaning that these components will always be a part of the revision tag. This is to make sure that your dev and prod sync up.
A way I've done in the past two have them be different is to set the time in dev to what you expect it to be in prod as the last step before a revision tag. Then, push the revision tag and change dev back to the time settings I wanted to dev. This obviously includes extra steps in the cutover and potential issues with test data in dev but can be used as a workaround.