Distribution packaging is no longer active with #3266927: End Install Profile Packaging on Drupal.org in August 2023

We can now:

  • Remove the packaging code
  • Remove drush make and other supporting code
  • Replace the packaging whitelist API with a static file of its final state, and update documentation/etc to make it clear that the project is obsolete
  • Look at simplifying the Views that list releases on project pages

Issue fork drupalorg-3388668

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

drumm created an issue. See original summary.

dww’s picture

The end of an era. 😉 Thanks for cleaning up the mess I helped create. 😅

  • drumm committed 1eeb26f7 on 7.x-3.x
    Issue #3388668: Remove project_verify_package
    

  • drumm committed ee6bd3ba on 7.x-3.x
    Issue #3388668: Remove drush make distribution packaging plugin
    

  • drumm committed a6018b34 on 7.x-3.x
    Issue #3388668: Remove unneeded dependency
    

  • drumm committed a6018b34 on d7-eol-warning-block
    Issue #3388668: Remove unneeded dependency
    

  • drumm committed ee6bd3ba on d7-eol-warning-block
    Issue #3388668: Remove drush make distribution packaging plugin
    

  • drumm committed 1eeb26f7 on d7-eol-warning-block
    Issue #3388668: Remove project_verify_package
    

  • drumm committed e63e6951 on 7.x-3.x
    Issue #3388668: Remove unneeded dependency
    

  • drumm committed b69c5c9b on 7.x-3.x
    Issue #3388668: Remove unneeded dependencies
    
drumm’s picture

Somehow Features is detecting drupalorg_forum as depending on this, unless the taxonomyextra field instance & base are removed. Since that field is leftover from a migration years ago, removing it is easier than figuring out why.

  • drumm committed c5f503af on 7.x-3.x
    Issue #3388668: Remove taxonomyextra field which causes Features to...

  • drumm committed 97848fde on 7.x-3.x
    Issue #3388668: Remove remaining references to taxonomyextra
    
drumm’s picture

Before removing the API & data for the packaging allowlist, we should make sure it is not updated. We can remove the Packaging whitelist maintainer role. For posterity, people with the role were:

No packaging allowlist entries have been updated in the past year.

  • drumm committed 4014c261 on 7.x-3.x
    Issue #3388668: Remove Packaging whitelist maintainer role
    

  • drumm committed 62820367 on 7.x-3.x
    Issue #3388668: Remove API & unnecessarty files
    

  • drumm committed be26e448 on 7.x-3.x
    Issue #3388668: Removed too much
    

  • drumm committed 70e95302 on 7.x-3.x
    Issue #3388668: Remove packaging allowlist listing
    

  • drumm committed 41fe3b02 on 7.x-3.x
    Issue #3388668: Remove permissions for packaging allowlist
    

  • drumm committed d8e9092e on 7.x-3.x
    Issue #3388668: Remove remaining packaging allowlist code
    
drumm’s picture

The packaging allowlist is now gone. The last piece is the “Releases missing security updates” display of the drupalorg_project_downloads View. That should no longer be needed.

  • drumm committed 9238f162 on 7.x-3.x
    Issue #3388668: Remove “Releases missing security updates”
    
drumm’s picture

Status: Active » Fixed

I think the best thing to do is remove “Releases missing security updates.” It may be possible to simplify more in project_release_compute_update_status() and the other displays of the project downloads, but I don’t think that would be worthwhile now.

The only releases made in 2022 or later that will be removed from project pages are:

  • openfed 7.x-2.44
  • real_estate_lp_profile 8.x-1.0-alpha2
  • responsive_blog_theme_installation_profile 7.x-1.4
  • openatrium 7.x-2.652
  • guardr 7.x-2.57

Query for the others: SELECT n.nid, n.title, from_unixtime(n.created) FROM node n INNER JOIN field_data_field_release_update_status fdf_rus ON fdf_rus.entity_id = n.nid AND field_release_update_status_value > 1 INNER JOIN project_release_supported_versions prsv ON prsv.recommended_release = n.nid AND prsv.supported = 1 INNER JOIN field_data_field_release_category fdf_rc ON fdf_rc.entity_id = n.nid AND fdf_rc.field_release_category_value IN ('current', 'legacy') INNER JOIN field_data_field_release_build_type fdf_rbt ON fdf_rbt.entity_id = n.nid AND fdf_rbt.field_release_build_type_value = 'static';

Status: Fixed » Closed (fixed)

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