Correct the Default, out of the box Numeric Revision Scheme

[The_Angry_Elf]

Add a "0" as the first revision to the numeric scheme as opposed to the current "1".

More often than not initial releases are released at revision "0", not revision "1".

How was this missed?

Every time I did an install or have to do an install and the client uses a numeric revision scheme, I have to create a custom scheme to add in the zero for initial released files.

[Boorda]

I agree!  Also same issue with the Alpha revision schemes.

Our company doesn't consider the first release as a revision, a revision to us is a change after first release to production.

My question is why even fire the rev bump when a file is added to Vault in the first place?

Let the revisioning system control the bumps via life-cycle or the Change Revision button. 

Great idea @The_Angry_Elf