On Sat, Feb 28, 2009 at 2:26 PM, Karim Ratib <karim.ratib@gmail.com> wrote:
Hello all,
I've been maintaining a module that I now feel would be better bundled with its parent module, which I also maintain. Specifically, the Workflow Graph (http://drupal.org/project/workflow_graph) module is tiny and depends totally on Graphviz Filter (http://drupal.org/project/graphviz_filter).
I have added the Workflow Graph files to the latest release of Graphviz Filter, and I would now like to close the Workflow Graph project page (and CVS folder too if possible). My question is: what's the best practice to do so? How would that affect running instances of Workflow Graph (which in this case, are only a handful)?
If it was me, I would do the following: - Check the code from the module to be obsoleted into the parent module. - Do a tag and release for it for the version(s) that are available of the old module. - Then go into Edit then Releases and uncheck all the releases that you have. - Put a big notice on the project saying "this is now part of XYZ", and the steps needed to switch. - Keep the project node published for a while, so users would know. I think that the users of the module will not see "revoked" or something like that, and will go to the project and know what is happening. Since graphviz is required by workflow graph, they will also get a notice to upgrade the module via update/update_status.
Thanks for your advice, K.
-- Khalid M. Baheyeldin 2bits.com, Inc. http://2bits.com Drupal optimization, development, customization and consulting. Simplicity is prerequisite for reliability. -- Edsger W.Dijkstra Simplicity is the ultimate sophistication. -- Leonardo da Vinci