In other systems we've used, the given revision of a page progresses through the minor version (1.1, 1.2, .1.2), until a publishing event creates the next major version 2.0, at which point the minor versioning continues (2.1, 2.2, etc.).
I'm trying to figure out what CQ's behavior is. I see that if no label is provided, the next revision is automatically set as the next minor version of 1.0. When I activate the page, it just creates another minor version. When will the page jump to v2.0?
As a test, I created a new version and set its label to "2.0" (it would normally have incremented up to 1.3 if I hadn't set anything). I then activated the page. I then saw that the activation created a new version at 1.4 (not 2.1).
I continued to create versions up to 1.10 thinking that might push it to 2.0, but no, 1.11 was created after activating. Will the page ever move to the next major version number? I haven't found anything in the docs that mentions how this might be configured.
Thanks for any help!
