Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This packages our zip and tgz releases. It works with Git-related-modules to check out code from repositories. We should modernize this to be a drush command.
Comments
Comment #1
drummThis issue also covers any updates to the project_release_node_rebuild_metadata table. Information from that is shown on release node view, but this script is in charge of populating and using values. It may be replaced with a field.
Comment #2
dwwMaking this a drush command has been on the roadmap since #980390: Port package-release-nodes.php to a drush command -- I'm definitely +1 for that.
The {project_release_node_rebuild_metadata } table was added at #1401990: Record a 'rebuild_version' for release nodes that are rebuilt -- it's the thing that remembers the specific version a given -dev release was re-packaged as (e.g. something like "7.x-2.0-rc3+17-dev").
This is definitely a launch-blocker, bumping to critical.
Comment #3
drumm#381956: Mark project releases as "to be updated" only if pushes happen there is also related. Currently, I'm focusing on making a drush command work for manually packaging a single project. When that is good, we'll want to use D7 core's queue for automated packaging.
Comment #4
drummI pushed a few commits for this. Notable changes are
The main work left is
Comment #5
drummDrupalorg followup: #1824414: Update release_packager plugins for D7
Comment #6
Senpai CreditAttribution: Senpai commentedAssigning to @drumm for completion of this one and the follow-up #1824414: Update release_packager plugins for D7 issue above.
Comment #7
drummI committed some more code for this and basic packaging a release is working. Leaving open for re-packaging.
Comment #8
drummanother tag
Comment #9
drummThe prerequisites for this issue, and packaging queuing is now done. #1878418: Queue release packaging at git code arrival is a followup.