Major version of the page

I couldnt see any configuration for the same in ConfigMgr. I think, to achieve this we need to write our own customize com.day.cq.wcm.core.impl.VersionManagerImpl

Hi,

AEM is not a version control system, so pages do not have the concept of versions. The label is just a declarative label, and it does not need to follow any specific format. If you would like to implement that, feel free.

To implement it, I would create a workflow, which first creates a version of the page with the appropriate label (=major version), and then replicates it. If the the page has been just versioned, replication does not create a new version (well, I am not 100% sure, would need to test).

Kind regards,
Jörg

Thanks Jorg,

I see that works if user keeps numbering manually. As soon as you create a version without label it will be another 1.xx.

I wonder is there way to make a true major version of the content, combined with publishing or launch?

Regards, 

Nikolai

but not a 'major' version. The version numbering continues as 1.xx not 2.0

OOB, every publish/activate of the page creates a version.