Close down Drupal 7 issues

Created on 6 December 2024, 12 days ago

Problem/Motivation

There are too many issues in the issue queue, 290 out of 480 are tagged as being Drupal 7 specific.

While the Drupal 7 version of the module isn't completely unsupported we should consider that it's only really very minimally supported for the next month or so, and so we should close down the Drupal 7 specific issues, except those we might consider critical or trivial to resolve to provide compatibility with PHP versions.

In about a month Drupal 7 is going to be EOL'd by the Drupal community, and so D7 VDE will likely become unsupported at that time anyway.

Proposed resolution

Close issues that are:

  • For the Drupal 7 version of the module
  • Not showstoppingly critical
  • Not about compatibility with modern PHP versions

Remaining tasks

  • Write a short: 'sorry but I'm closing this' message, and add it to this issue for easy copy/pasting.
  • Go through all the Drupal 7 issues closing them down if appropriate, and referencing this ticket.
📌 Task
Status

Active

Version

3.0

Component

Code

Created by

🇬🇧United Kingdom steven jones

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @steven jones
  • 🇬🇧United Kingdom steven jones

    Sorry for the lack of attention to your issue, please accept my apologies.

    Drupal 7 is going to be end-of-life'd by the community in approximately 1 month.

    As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on 📌 Close down Drupal 7 issues Active .

    If you feel like this issue has been closed by mistake, please do comment about re-opening it.
    If you feel like the ticket is still relevant for the 8.x-1.x version of the module, the please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.

    Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated and the Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :)

    Which was:

    Sorry for the lack of attention to your issue, please accept my apologies.
    
    <a href="https://www.drupal.org/about/drupal-7/d7eol/partners">Drupal 7 is going to be end-of-life'd by the community in approximately 1 month.</a>
    
    As such, I am closing all non-critical looking, non-PHP compatibility issues for Views Data Export to tidy up the issue queues and reduce the noise. You can read about this on 
                
                  
                  
                  📌
                  Close down Drupal 7 issues
                    Active
                  
                .
    
    If you feel like this issue has been closed by mistake, please do comment about re-opening it.
    If you feel like the ticket is still relevant for the 8.x-1.x version of the module, the please search for a duplicate issue first, and if there really isn't one (and you've looked properly) then change the version on the ticket and re-open.
    
    Thanks to everyone involved in this issue: for reporting it, and moving it along, it is truly appreciated and the Drupal community wouldn't be what it is today without your involvement and effort, so I'm sorry that we couldn't get this issue resolved. Hopefully we'll work together in a future issue though, and get that one resolved :)
    
  • 🇬🇧United Kingdom steven jones

    I've closed down all the issues except for:

    Which seem like issues we should resolve in the next little while and do a final 7.x-1.x release I think.

Production build 0.71.5 2024