Permission for branch version creation

[boris-horner]

In some cases, branch versions are unwanted and the system should forbid to create one. A flexible way to do this is by adding a new permission BRANCH to the existing VERSION permission.

• VERSION means, the user may create a new version of the object without creating a further branch (or in other words: the new version has as many dots in its number as the original version). So, versioning a branch version is covered by this permission.
• BRANCH means, the user may create a new branch (or in other words: the resulting version has more dots in the version number than the original version)

To maintain the same behaviour as before, all ACL entries with VERSION allowed should have VERSION and BRANCH allowed with the new set of permissions.

Note: Users have no choice whether to branch or not. They issue a version command and depending on whether there is a successor version or not, the system will branch or create a new trunk version. The client should behave accordingly.

If the user may not WRITE_CONTENT and has VERSION permission, but not BRANCH permission:

• If the object has no successor, the client should allow checkout (because the user could create a new version on checkin).
• If the object has a successor, versioning would result in a branch the user lacks permission to create. Checking in as same version is not allowed either. So the client should not allow checkout in the first place, since no checkin is possible.

[dewarim]

Suggestion for naming: VERSION_HEAD_ONLY -> versioning only allowed for head VERSION_HEAD_AND_BRANCH -> versioning allowed for head and branch versions

migraton:

• change version to version_head_and_branch via SQL
• add version_head_only permission to code & permissions table

[boris-horner]

Lieber als Zweites nur Branch_only, damit man nur das gezielt erlauben kann.

Get Outlook for Android

From: Ingo Wiarda @.> Sent: Friday, September 10, 2021 4:45:12 PM To: dewarim/cinnamon @.> Cc: boris-horner @.>; Author @.> Subject: Re: [dewarim/cinnamon] Permission for branch version creation (#199)  

Suggestion for naming: VERSION_HEAD_ONLY -> versioning only allowed for head VERSION_HEAD_AND_BRANCH -> versioning allowed for head and branch versions migraton:

change version to version_head_and_branch via SQLadd version_head_only permission to code & permissions table — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.