To reproduce the problem:
Select a document Rev 1 in master and send to project. Will create Rev 1.0
Send to portal. Will arrive as 0.1
Change the document content, will create 0.2
Send back to meridian. Revision will be 1.1
Ideally revision number should be sync between portal and power, otherwise it is little confuse to understand the revision system.
See also MER-I-387
If it were possible that the minor revision would climb every time a change to the document content is implemented while within a projects state
Thanks for this feedback, Irineu. I have added this story to our roadmap for prioritization and planning.