renaming a module?
lefnire - October 6, 2008 - 04:29
Since I can't rename my module in cvs, I'd have to open a new module, give the old module some "deprecated" language & a link to the new one. On a scale from 1-10, 1 being permissible and 10 being anathema, how bad is this?
My module is webform_pdf, and after working with webform for a while, I've realized it was designed for simplicity and I'm beating all around the bush to push its limits. It should be cck-compatible instead. So I want to rename it to fill_form to be general. I'd leave it the way it is, except for the fact that I'm going to drop webform support in favor of cck altogether, so the name will be 100% misleading. Any ideas?
=-=
seems to me if you are making those kinds of changes you can start a new project and leave the old one as is and it can be added to the abandoned module user. If someone else comes along and wants to maintain at a later date for webform. so be it. no ?
the other option would be to remove the realeases from the project page and annouce the intentions there as well, pointing to the new module.
you may want to figure out an upgrade path from one to the other so users who want to switch don't get left behind.
Glad you see my reasoning!
Glad you see my reasoning! I was expecting angry developers is why I asked before I did anything :)
Web development & design podcast