So, I've got a question pointed by a services module discussion.. What should be the best practice for contributed module versioning when Drupal version is updated, keep current contrib versioning?
I mean, lets say we do have customproject versions 1.x and 2.x for Drupal 6. The customproject-6.x-1.x branch is currently in bugfixing status, and customproject-6.x-2.x is the rock&rolling version. When releasing a D7 upgrade, customproject 1.x will never have a 7.x version, should customproject-7.x-2.x be kept as initial version for consistency? or do we kindly rename it to customproject-7.x-1.x for the upgrade?
I'm asking this because now there are plenty of contrib modules with 1.x branches in bugfixing status, and many other contrib modules with 3.x as current version.. Updated modules will be release with initial branch numbers as 2 or 3.. I wonder what will happend when D8 is released.
so.. suggestions?
Comments
If new functionality, new 2.x version
So IMO, 1.x should refer to the same feature set across Drupal versions. So if the feature set changes, move to a new contrib version.
6.x-1.x has same feature set as 7.x-1.x
7.x-2.x has new feature set.
takes a difficult road
That can make a difficult road for folks in the long run, especially for some maintainers who bump their version number frequently. If you have 2 or 3 releases per core release than by Drupal 10 most everyone will be on 10.x-15.x. Whether it makes sense or not, I think people like low numbers and my feeling is that the first release for a module that is compatible with a new version of core it should be 1.x
So, if you have 6.x-3.x then porting that branch to 7.x would make 7.x-1.x.
knaddison blog | Morris Animal Foundation
Who else on this earth resets versions?
You shouldn't either.
As already explained in Best practices for co-maintaining projects, the major version of a module refers to a certain feature set.
Do you know of any software that suddenly flips back to version 1? Just because some other software changed its version?
That's insane.
If you create too many major versions, your fault. Try to explain that to your users. #fail
Daniel F. Kudwien
netzstrategen