With #779476: Remove commit restrictions for installation profiles long complete, http://drupal.org/project/cod, http://drupal.org/project/cod_support and http://drupal.org/project/fusion_swimmingly can live in the same project, which simplifies development and makes it easier for folks to file issues.

Let's consolidate these projects.

Comments

ezra-g’s picture

I'm actually not clear on how to accomplish this :P.

It would be ideal to preserve the usage statistics data for COD which is currently recorded against COD_Support, but to use the COD shortname.

Some potential options are:

A) Change the COD_Support project shortname to COD, change the COD shortname to something like COD_Deprecated?
-- Can we do this?
-- What will happen to the existing sites whose info files that have "project = "cod_support"?
B) Something else ;) ?

dww’s picture

I'd suggest just doing the right thing and letting the new usage stats start showing up as you move forward and people upgrade. So:

  • Move all the code out of cod_support and put it directly into cod. There are ways to do this that preserves all the Git history if you'd like.
  • Leave the cod_support project where it is, but with an empty Git repo (or perhaps just a README.txt or something). Mark the project node "obsolete", and add a note saying "as of COD version X and higher, this module is no longer needed since it has moved directly into the COD project itself."
  • Usage stats will continue to report to cod_support for existing sites in the wild (you can't change those now).
  • New usage stats will properly appear on cod itself once people upgrade or install new sites using the latest version.

Anything else would be uncivilized. ;)

Cheers,
-Derek

ezra-g’s picture

Status: Active » Fixed

Thanks!

After further thought, it actually makes sense to allow folks to download just the COD feature modules separately from the packaged distribution.

We've made a full release over at http://drupal.org/project/cod, so marking this as fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.