On hook_update_N() the documentation says:
mymodule_update_7000(): This is the required update for mymodule to run with Drupal core API 7.x when upgrading from Drupal core API 6.x.
mymodule_update_7200(): This is the first update to get the database ready to run mymodule 7.x-2.. Users can directly update from 6.x-2. to 7.x-2.* and they get all 70xx and 72xx updates, but not 71xx updates, because those reside in the 7.x-1.x branch only.
Is it really mandatory to define an 7000 update hook? I saw some contributed module updates that starts with 7300, when the module version for Drupal 7 is 7.x-3.x.
I am a bit confused, because I read before the UPGRADE.txt file for Drupal 7 core that says:
MAJOR VERSION UPGRADE
To upgrade from a previous major version of Drupal to Drupal 7.x, after following the instructions in the INTRODUCTION section at the top of this file:
- In addition to updating to the latest available version of Drupal 6.x core, you must also upgrade all of your contributed modules for Drupal to their latest Drupal 6.x versions.
For me, it means that users can't directly update from 6.x-2.x to 7.x-2.x unless 6.x-2.x module was the latest in the Drupal 6.x versions. Is this correct?
What about eventual database updates defined by 7.x-1.x branch? Do they have to be reported in the 70xx updates?
Can a module version 7.2.x keep any other updates (e.g. 60xx, 71xx) or it should be clean and defined only updates about 70xx and 72xx?