[development] Module retirement?
dries.buytaert at gmail.com
Sat Oct 7 10:17:20 UTC 2006
On 07 Oct 2006, at 00:19, Greg Knaddison - GVS wrote:
> I'd say that the *most responsible* thing is to provide a "smooth"
> path to get your users into the new modules and then retire the
> current ones. This happens pretty often - see:
> If you just say "module is retiring, use X instead" and don't provide
> an upgrade path then that's OK too. It's certainly better than just
> dropping it and leaving people hanging. If possible document the
> manual steps to move to the module, but ideally provide code that will
> take current data in the module and move it to the format needed by
> the replacement module.
> You could also offer on the project page to let someone else
> update/maintain the module if they are really tied to it - maybe
> somebody likes your module more than the replacements.
I agree with all of Greg's suggestions. They have everything to do
with being a responsible maintainer:
Thanks for trying to be responsible AjK. Much appreciated. :)
Dries Buytaert :: http://www.buytaert.net/
More information about the development