Details

    • Bug Priority:
      Category 2
    • ACT Numbers:

      15024-28944

      Description

      Alfresco tracks minor versions as 0.X and major versions as Y.0. If a developer explicitly creates a version as a minor version through the version service (Java or JavaScript), the version label starts at 1.0 instead of 0.1. If you set the cm:initialVersion property to be false and the cm:autoVersion to be false. I would expect on a service call to createVersion(...) with majorVersion=false would create a version as 0.1. It's counter intuitive that you say that all major versions are X.0 and have one minor version as 1.0. This seems to be a design flaw.

      It would appear that a fix would involve changes to:-

      • org.alfresco.repo.version.common.versionlabel.SerialVersionLabelPolicy
      • Potential changes to policy behaviour so when cm:versionable is added, a version isn't automatically created as a major version.

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  closedbugs Closed Bugs (Inactive)
                  Reporter:
                  j.portillo Jose Portillo (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel