[development] Old module update functions
drumm at delocalizedham.com
Mon Dec 8 20:26:29 UTC 2008
Drupal core does keep the code for two major version updates. However,
that full 2-version upgrade path is not well-tested since core
developers rarely do it. Updates sometimes use the API at the time,
and the API can change. This could potentially be covered by unit
tests. So go ahead and try upgrading 2-versions if you need to, but
keep a backup.
For modules, you should provide what you can support. Keeping 2 major
releases is a good place to start, but feel free to do what works for
you and your module's users.
On Mon, Dec 8, 2008 at 10:32 AM, Arancaytar
<arancaytar.ilyaran at gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> As far as I know, updating by more than one major release at once is not
> supported in core (old update functions are removed from newer branches)
> - - so you can probably do the same in contrib.
> On 08.12.2008 19:25, Eric-Alexander Schaefer wrote:
>> Hi List,
>> is it save to remove old update functions from module.install. E.g. is
>> it safe to remove D5-based update functions in D6 versions?
> - --
> Nothing beside remains. Round the decay
> Of that colossal wreck, boundless and bare,
> The lone and level sands stretch far away.
> - ---------------------------------------------
> AOL: realarancaytar / 282026638
> XMPP: arancaytar.ilyaran at gmail.com
> PGP: http://ermarian.net/downloads/0x27CA5C74
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
More information about the development