Drupal 6 end of life is publicised as 24th Feb 2016. I'd like consideration for this to be extended by 6 months. As of today:

  1. Drupal 8 has seven critical errors
  2. One of my typical websites has 23 modules which hav no available releases for Drupal 8, and 17 still in development. Only 15 modules are ready for Drupal 8, less than 30%.
  3. Token is currently in alpha release
  4. The Date API is missing some functions (ref)
  5. Pathauto is currently in alpha
  6. Calendar in development (pre-alpha)
  7. Webforms in development (pre-alpha)
  8. Drupal Upgrade is still under development
  9. Rules is in development (pre-alpha)
  10. There is also no migration path from the recommended Views 6.x-2.x branch (which has 6 times as many installations as Views 6.x-3.x), and the home page says that upgrading from Views 6.x-2.x to Views 6.x-3.x has an upgrade bug.

Comments

iantresman created an issue. See original summary.

pwolanin’s picture

pwolanin CreditAttribution: pwolanin as a volunteer and at Acquia commented
Status: Active » Fixed

see:https://www.drupal.org/node/2646980

cilefen’s picture

cilefen CreditAttribution: cilefen commented

Drupal 6 has two pages of Critical issues. I don't understand that argument.

The community is not going to support Drupal 6 but there are paid vendors you can use.

You are totally right about module readiness, but there has always been the option of upgrading to Drupal 7.

Respectfully, it is easy to open an issue like this but who among the volunteer community is going to be able to drive Drupal 8 forward while supporting two older versions?

Status: Fixed » Closed (fixed)

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