The "Latest Drupal Core Releases Block" is totally outdated as it obviously doesn't evaluate the actual releases. Even the latest dev release says:

  • 5.x: old stable Drupal version - supported
  • 6.x: current stable Drupal version
  • 7.x: development version - not supported

This is total bogus; correct would be:

  • D5 is unsupported
  • D6 is still supported
  • D7 is the current stable Drupal version
  • D8 is the current development version

As it is, the "Latest Drupal Core Releases Block" is total nonsense as is does not display the Latest Drupal Core Releases.

CommentFileSizeAuthor
#1 1364896-update-drupal-version.patch666 bytesmavimo

Comments

mavimo’s picture

StatusFileSize
new666 bytes

This patch solve the problem, can you confirm?

asb’s picture

Thanks for the patch Marco, but I believe it is not really feasible to hardcode status information into the module because it's already in the packages if you query for the API version (e.g. http://updates.drupal.org/release-history/drupal/8.x). Wouldn't it be better to use the packaging data, like 'Update Status' or 'Drush' does? Example:

# drush rl drupal
------- RELEASES FOR 'DRUPAL' PROJECT -------
 Release         Date         Status                            
 6.x-dev         2011-Nov-23  Development                       
 6.22            2011-May-25  Supported, Recommended
 6.21            2011-May-25  Security
...
 7.x-dev         2011-Dec-06  Development                         
 7.10            2011-Dec-05  Supported, Recommended
 7.5             2011-Jul-27  Security

This would turn around the logic a bit, but should always show which release is current and supported, which security updates are available, and where the development is taking place. What do you think?

uccio’s picture

Assigned: Unassigned » uccio
Status: Active » Fixed

Fixed,

the new version are now availlable!

Status: Fixed » Closed (fixed)

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