there's no reason for you to be burning through major revision numbers like this for your module. major revisions are for whole new sets of functionality, an entire release "series". i think you mean to be incrementing the patch level (the final digit) of the release. as far as i can tell, you should be on version 4.7.x-1.3 or so by now.

if you happen to be adding new features to 4.7.x-compatible code, you just need a 4.7.x-2.* series, with maybe a couple of releases from there (e.g. maybe you'd be up to 4.7.x-2.1 or 4.7.x-2.2 by now). see these docs:

http://drupal.org/handbook/cvs/releases
http://drupal.org/node/93999

thanks,
-derek

Comments

Dublin Drupaller’s picture

Dublin Drupaller commented
Status: Active » Closed (fixed)

sorry Derek.

Didn't spot anything in the docs about numerous major releases causing any problems. I was strapped for time today to be honest, but, when I get time, I'll try and go through all those docs again.

anyone else stumbling across this thread....recommend you add the following to your reading material: http://www.angrydonuts.com/my_informal_take_on_using_the_ne

It's a very good write up and while I'm still struggling with the new release system, that helped me get it working for Drupal 5.x module updates.

Dub

Dublin Drupaller’s picture

Dublin Drupaller commented

sorry Derek.

Didn't spot anything in the docs about numerous major releases causing any problems. I was strapped for time today to be honest, but, when I get time, I'll try and go through all those docs again. It might be worth updating those docs, so it's very clear.

anyone else stumbling across this thread and are similarly stumped....recommend you add the following to your reading material: http://www.angrydonuts.com/my_informal_take_on_using_the_ne

It's a very good write up and while I'm still struggling with the new release system, that helped me get it working for Drupal 5.x module updates.

Dub