Historically Commons has used the Commons release project to track usage statistics of Commons.
We can track usage statistics against the main Commons project as long as it has a release of some kind (even one that does not contained a packaged distribution) and the proper information in the feature module's info files. This is even easier to provide now that #779476: Remove commit restrictions for installation profiles is fixed.
Also, Commons_release unsets update status information for contributed projects included with Commons with has 2 negative effects:
- Site admins aren't notified of new versions of the contrib projects, including security releases
- Sites running Commons do not report usage data to the underyling contrib projects. For example: OG Features would appear to be running on ~98 sites, but in fact is a dependency for all Commons 2.x sites, of which there are several times that number.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 1335870-commons-remove-commons-release.patch | 2.04 KB | ezra-g |
| commons-remove-commons-release.patch | 1.66 KB | ezra-g |
Comments
Comment #1
ezra-g commentedWe should actually uninstall commons_release, not just remove it from the codebase.
Comment #2
ezra-g commentedHere's a revised patch.
Comment #3
ezra-g commentedThis is committed: http://drupalcode.org/project/commons.git/commitdiff/37568e6?hp=2f1a8c36...