This issue is for recording our plans and decisions with respect to user data upgrade paths from Scheduler D6 to D7? Specifically the points are:

  1. Currently all hook_update_N() functions have been removed from the first D7 scheduler.install which I think means that we are assuming that a user will have had to upgrade to the latest 6.x release (currently 1.8) before converting to 7.x-1.0
  2. When there are later updates after 7.x-1.0 is released, will these have to be added to the D6 branch also?
  3. What mechanism is there to ensure/force that the user is upgrading from the latest 6.x version, so that no db updates are missed

Comments

eric-alexander schaefer’s picture

eric-alexander schaefer commented

We could just put the D6 upgrade functions back into scheduler.install. Are they called before the upgrade to D7?

eric-alexander schaefer’s picture

eric-alexander schaefer commented

According to http://api.drupal.org/api/drupal/modules--system--system.api.php/functio... only update functions older than two major releases of Drupal should be removed.

eric-alexander schaefer’s picture

eric-alexander schaefer commented
Status: Active » Fixed

http://drupal.org/cvs?commit=499326

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.