Using "no update" version option for documents

It's common use that a letter (starting on "A") is used as revision index while the document is rejected by the customer. But once the doc gets approved by the client, the revision index changes to a number (starting on "0"). Following versions would be 1, 2...
Is this something that can be taken into account?

No ...

But you may use minor versionh to help
V1.0_draft1 => internal review => rejected
V1.0_draft2 => internal review => approved
V1.0 => external review => refected
V1.1_draft1 => internal review => rejected
V1.1_draft2 => internal review => approved
V1.1 => external review => approved => set version V1.1 as reference (validated version)
later, you may work on V2.0 for changes on doc...

I don't want to get kicked off the forum by mad babynus

Who's mad ?
My doctor told me I was OK, and to prove it he gave me a beautifull white shirt, with buttons in the back and very long sleeves.
Yes really a very smart shirt...

Not even if someone filled in a proposal for evolution regarding a brand new "industrial" evolution type?
It could wait until v4.0 (or even 4.x), to come along with the other workflow improvements

I recorded the request as Ticket #1119, for version V4.x.
The V4.x versions are not planned yet, but sure will not be deployed before 2015...