Hopefully as far as effort goes, this shouldn't be too bad.
In Vault Administration Settings, there's an option to 'restrict item lifecycle changes to change orders'.
I get this, it's useful, we don't want people changing Item lifecycles willy nilly.
However, when this is enabled, I'm forced to raise an ECO to release an Item for the first time at revision 0. Why? Well because it's a lifecycle change, so the settings impacts it. Yes but it shouldn't, not on this particular lifecycle change.
I can only summise that this is a mistake, someone implemented the functionality but didn't understand the engineering change process. Under no circumstances do you raise an ECO to release an Item that hasn't been made yet. It's revision 0, it's new, brand new, being forced to raise a 'change order' against it just so I can release it is... it's a mistake, an error, please change this. I'm sick of trying to explain why this needs to happen to hundreds of engineers who are as confused about it as I am, and I don't have an answer for them.