-
Bug
-
Resolution: Won't Fix
-
Major
-
3.5
-
None
-
None
Versions of a version history are usually incremented this way : 1.0, 1.1, 1.2, ...
When unarchiving a content, the next checkpoint will create a new branch in the version history. Which means that the new version is named 2.0 and its predecessor is the root version and not version 1.2.
I am not sure whether or not this is a bug, but I guess this is not expected and could perhaps show to have some undesirable side effects.
More details are availables in the JCR specs :
- Repository Model $3.13.5 Version History
- Versioning
[CMS-4213] New version of a unarchived content creates a new branch in the jcr version history.
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Fix Version/s | New: 4.2.0 [ 14425 ] | |
Fix Version/s | Original: 3.LATER [ 10121 ] | |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Fix Version/s | New: 3.LATER [ 10121 ] |
Fix Version/s | Original: 3.5 [ 11387 ] |
Assignee | New: Nicolas Gavalda [ ngavalda ] |
Fix Version/s | New: 3.5 [ 11387 ] |