[development] 5.x to 6.x migration timeline, best practices, tips

Nathaniel Catchpole catch56 at googlemail.com
Tue May 19 17:55:27 UTC 2009

Because changing those instructions to "Do a diff between all the core
.install files to check for schema changes between the release you're
currently on and the latest stable release, if there have been any updates,
upgrade to the latest stable first, if not, proceed directly to 6" wouldn't
make any sense to 90% of people?


On Tue, May 19, 2009 at 5:29 PM, Earnie Boyd
<earnie at users.sourceforge.net>wrote:

> Quoting Nathaniel Catchpole <catch56 at googlemail.com>:
>  The only reason to upgrade from 5.x to 5.latest-stable would be if there's
>> been schema changes in a minor version. This is very rare, but sometimes
>> necessary - however it's easy to check by comparing system.install between
>> 5.0 and 5.18 to see if any new hook_update_N() has been added.
> Really?  Then why is it documented practice?
> <quote reference="http://drupal.org/upgrade/">
> 1. Upgrade to the latest minor version in the major version you're
> currently on (e.g. if you are on 5.5 and want to upgrade to 6.10, and there
> is a 5.12 version out, upgrade to 5.12 first).
> </quote>
> --
> Earnie
> -- http://r-feed.com/           -- http://for-my-kids.com/
> -- http://www.4offer.biz/       -- http://give-me-an-offer.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.drupal.org/pipermail/development/attachments/20090519/17eec4b8/attachment-0001.htm>

More information about the development mailing list