Correct version numbers
overall - June 21, 2009 - 22:53
| Project: | Drupal.org infrastructure |
| Component: | CVS |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
(sorry for my english)
BitTorrent module version numbers need to be corrected, because it has a gap in the module version sequence
6.x-9.x-dev
6.x-9.0-beta1
6.x-10.x-dev
5.x-2.0-beta3
5.x-2.0-beta2
5.x-1.x-dev
5.x-1.0-beta
After 2.x we at once go to 9.x, and then to 10.x.
How can I correct this in CVS, if I can. If I cannot, who can?
And should I rename corresponding implementations of hook_update_N(), i.e. "bt_tracker_update_6903()" ?
What will be with users that currently using versions with the current numeration?
Thanks.
#1
#2
#3
It looks like you are using the wrong version numbering scheme - do you really intend to have 10 branches????
Generally the progression is 6.x-1.0 to 6.x-1.1 ... 6.x1-1.10
#4
As I wrote in first post:
Of course this gap was made by accident... (and not by me).
So, how can I correct this issue. If I can. If I cannot, who can?
Thanks.
#5
Use the correct branch that you want to and mark all the other branches as unsupported on the project edit page?
#6
There are users that are already using 6.x-9.x releases (furtunately not so many - 45).
So could this "rollback" produce some errors for them (for example on updating)?
#7
I am marking this report as fixed because it has already gotten a reply.
#8
Automatically closed -- issue fixed for 2 weeks with no activity.