There are a few more things to figure out before we create an official release. The most interesting one is based on a suggestion in IRC that we rename the omniture module to site_catalyst since Adobe bought the product and technically "Omniture" no longer exists.
We definitely DO NOT want to create a release for omniture and then rename it after the fact, so we should either go ahead and rename the module now, or accept that it will not be renamed for D7.
Assuming we do rename the module I would create an update path (basically renaming all the existing variables in the variables table) for any sites that are already using the dev version.
Thoughts?
Comment | File | Size | Author |
---|---|---|---|
#4 | omniture-update-msg.patch | 788 bytes | bleen |
Comments
Comment #1
cmoad CreditAttribution: cmoad commentedI'm looking for a 7.x release and I would advocate for performing a rename of the module now and referencing the name Omniture in the description. Search engines will do the rest. Thanks!
Comment #2
lucascaro CreditAttribution: lucascaro commentedPersonally I think it would make sense to name it site_catalyst or rather sitecatalyst to avoid potential conflicts (#367355: Module names should not contain an underscore).
I say yay but I wonder if @greggles would have an opinion or comments on this?
Comment #3
bleen CreditAttribution: bleen commentedWork on this module has been moved to: http://drupal.org/project/sitecatalyst
The only thing left in this task IMO is to add an update message that tells existing users about this change...
Comment #4
bleen CreditAttribution: bleen commentedadded a message telling users to use the SiteCatalyst module