migrations prefix w/ rework? about rpg-boilerplate HOT 3 CLOSED

Everytime you re-work a function, you have to have a tag. If you're on a branch and working on it, then you just revert / deploy and modify it in place. If you've already deployed it, then that release was tagged. If you need to make a modification then you rework.

When you rework, it takes the current version, copies it and agives it a tag suffix, then makes the current revert script a copy of the now-old deploy script, and then you can modify the deploy script in place. So function_currentProfile always references the latest version, and there are old versions with tag suffixes auto-added to sqitch.plan which can be ignored.

from rpg-boilerplate.

Nope; I don't use sqitch so I was just commenting as a newcomer that I wasn't sure which order to look at them as. What happens if you rewrite a function a few times in different migrations?

from rpg-boilerplate.

I've reverted the previous migration prefixing, as I don't like it :)

from rpg-boilerplate.