How long after Drupal 6 becomes unsupported should all D6 projects be demoted? There are many D6 projects that state they're supported but haven't been touched in years. Once Drupal 8.0.0 is released and (after three months) D6 looses support there should be a bulk update for contrib too.

The EOL date for Drupal 6 is February 24, 2016.

Original post:
The vast majority of D6 Ubercart modules have not been touched since 2011, if not earlier, though most modules still are marked as being "actively maintained". Would it be possible to update all D6 Ubercart modules to have a status of "abandoned" if there has not been any activity in the past year?

Comments

lizzjoy’s picture

lizzjoy
she/her
Primary language English
Location Ann Arbor
commented
Issue summary: View changes

@DamienMcKenna, how many modules are you counting for this request? There are no tools to do bulk updates so any course of action depends on quantity.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

Maybe when D8 is released there should be a site-wide update to change the statuses of all D6 modules a to either abandoned or unsupported, depending on whether they have releases? This would obviously need to be an update script using the batch API.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Title: Bulk-update of project status to "abandoned" for D6 Ubercart modules? » Bulk-update of project status to "abandoned" for D6 modules?
Project: Drupal.org site moderators » Drupal Technical Working Group
Component: Site organization » Miscellaneous
Category: Support request » Task

Moving this to the TWG.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Title: Bulk-update of project status to "abandoned" for D6 modules? » [policy, no patch] How long to wait to bulk-demoted contrib releases after core release marked unsupported?
Issue summary: View changes
tizzo’s picture

tizzo commented

The TWG discussed this on our call today, we haven't reached any decision but is on the agenda for our next meeting and we will be following up here.

xjm’s picture

xjm
she/her
Primary language English
commented
Parent issue: » #2559711: [meta] Drupal.org (websites/infra) blockers to Drupal 8.0.0, 8.1.0, etc.
Related issues: +#2651570: Bulk update all 6.x issues to 'Closed (outdated)' when support is dropped

I believe this is the SWG's call under our governance. I believe the security team has already discussed this elsewhere but I could not locate it. I'd reach out to @mlhess.

xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes
mlhess’s picture

mlhess commented

They will lose security team support as soon as the next release comes out (or close to it if we feel the need to do one last release) .

tizzo’s picture

tizzo commented

After further discussion on our call today, and considering the comments posted earlier, the TWG will be consulting further with the SWG on this issue.

effulgentsia’s picture

effulgentsia commented
Related issues: +#2681323: 6.x contrib update status plan

See #2681323: 6.x contrib update status plan for recent discussion related to this.

effulgentsia’s picture

effulgentsia commented

Also, https://www.drupal.org/project/mydropwizard is an interesting project.

effulgentsia’s picture

effulgentsia commented
Status: Active » Fixed

The bulk demotion occurred, so as far as I know, there's no policy left to decide, so marking this fixed. See #10 and #11 for some of the follow-up work, but that's outside the scope of the TWG.

Status: Fixed » Closed (fixed)

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