Not releasing for 5: remove HEAD alltogether?
Hi there. I maintain two projects that have better options alread in 4.7, I spent that cycle to phase them out and don't plan a release for 5. Should I remove the HEAD version from CVS? (cvs remove, so still accessible, for those interested) Bèr -- Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: www.sympal.nl
Quoting Bèr Kessels <ber@webschuur.com>:
Hi there.
I maintain two projects that have better options alread in 4.7, I spent that cycle to phase them out and don't plan a release for 5.
Should I remove the HEAD version from CVS? (cvs remove, so still accessible, for those interested)
IMO, should anyone care about it, whether or not to remove from CVS depends on the reasons for not moving to 5.0. If the modules don't make sense for furture releases then yes I think they should be. If it is just the case that you no longer care to maintain it then I think the HEAD README.txt should be modified to say so and that a new maintainer is welcome to take on the task of conversion. Earnie
On Jan 2, 2007, at 2:01 PM, Bèr Kessels wrote:
Should I remove the HEAD version from CVS? (cvs remove, so still accessible, for those interested)
sure. if the code that matters is in the right branch(es) already (DRUPAL-4-7, DRUPAL-4-6, etc), and you don't plan on moving anything forward in the future, removing the versions in HEAD is a fine solution. especially since there are better alternatives out there already... i'm happy to see consolidation and merging of contrib modules, instead of more forks and splits. just be sure to explain this on your project node, in case anyone goes looking. you should also unpublish the HEAD release node (i'm pretty sure you have permissions to do that yourself). cheers, -derek
participants (3)
-
Bèr Kessels -
Derek Wright -
Earnie Boyd