I'm looking for clarification on the Drupal 6.24 release and Commons 6.x-2.4.

The release notes ( https://network.acquia.com/downloads/drupal-commons/6.x-2.4-release-notes ) say:

Commons_release module is deprecated
Historically, Commons informed site administrators about new version of Commons or contributed Drupal modules by way of the Commons release module. Beginning with version 2.4, the Commons release module is disabled. Instead, use the Update status information on your Commons site at http://[site_URL]/admin/reports/updates to let you know when new versions of Commons or contributed modules are available.

The notes block on https://network.acquia.com/downloads/drupal-commons says:

Always download a complete copy of Drupal Commons. Do not update contrib modules to their latest release independent of the complete distribution.

And now there is a note on the project page ( http://drupal.org/project/commons )

Note, to get the fully packaged version of Commons, download Commons from Acquia.com as the Drupal.org release contains only the Commons feature modules and does not contain Drupal core or contributed projects.

Is it correct to conclude that we can now upgrade anything that isn't a feature without waiting for a Commons release (and all the documentation hasn't cause up with this)? For example, is it ok to upgrade a Commons core from 6.22 to 6.24?

A document or note outlining management best practice would go a long way here!

Thanks.

Comments

dale42’s picture

G'ah, I always find more information after I post. *sigh*.

So the 6.24 answer is in this issue: #1425130: Update core to 6.24

Would still appreciate some general guidance on handling module updates in Common 2.4 and higher.

ezra-g’s picture

Status: Active » Fixed

In general, the best bet is to update Commons 2.x using the tarball from Acquia.com.

However, you can update Drupal Core and Contrib as long as you make sure to apply any patches specified in the Commons make file.

Marking as fixed, but feel free to re-open for further clarifications.

Status: Fixed » Closed (fixed)

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