0

I have created a module, and I have to change the permissions implemented (and used) from the module. Should I create a new major version (e.g. passing from 7.x-1 to 7.x-2), or is it fine to create a minor version (e.g. passing from 7.x-1.3 to 7.x-1.4)?

I am talking of a module for which there is already an official release, not of a module that has only a development snapshot.

Improve this question
0

2 Answers 2

Reset to default
1

If it changes significant behaviour from previous version I recommend changing the major version. Even if its just a single adjustment like permissions. Wrong or missing permissions may cause huge problems on a site running your module.

Improve this answer
1
  • I accepted this answer because user permissions are normally associated to routes, or to actions a user can take; introducing a new permission, or even using an existing permission instead of a new one previously used means to significantly change the module behavior. Often, new permissions mean new code added to the module, which could also mean a significant behavior change is introduced.
    – apaderno ♦
    Dec 20, 2021 at 10:28
0

I personally dont think that there should be a new branch for this altogether, or is required. We can very well get away with releasing an updated version of it, however if any Db changes are required, we will have to incorporate those as well.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.