[development] Incremental upgrades

Khalid Baheyeldin kb at 2bits.com
Sat Jul 28 00:10:38 UTC 2007


>
> On 7/27/07, Gabor Hojtsy <gabor at hojtsy.hu> wrote:
> > Cog Rusty wrote:
> > >> Well, update.php does not include older updates, so if one has an
> older
> > >> 4.x site (let's say 4.5 or 4.4), he cannot upgrade directly, but
> first
> > >> go to an intermediate version. I have not looked into it, but
> update.php
> > >> might have problems, or would not inform the user, if he has such an
> old
> > >> system that has no updates in the actual update.php
> /update.inc/*.install
> > >> files code.
> > >
> > > The question remains, because how would it help to upgrade such an old
> > > version first to 5.1 and not to 5.2?
> > >
> > > An advice which seemed safe so far was
> > > (a) never skip major versions
> > > (b) when stepping to the next major version use its latest minor
> > > version, assuming that it would be more "bug-fixed"
> >
> > Absolutely agreed.
>

Just to add in: I upgraded a few sites from 4.6 to 5.1. One had no issues
at all. The other had some issues mainly related to data set size (database
too big) and varbinary/UTF8.

But the point is: there was no need to install 4.7 and upgrade from 4.6 to
4.7 first, then install 5.1 and upgrade to that.
-- 
2bits.com
http://2bits.com
Drupal development, customization and consulting.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20070727/b5ffb43e/attachment.htm 


More information about the development mailing list