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.Sub-task for #322626: META: Package and version non-modules for download.
Once #1434476: Add project-type-specific settings for default version_format strings and #1434500: Add project-type-specific settings for label_version_mapper plugin are done, we're going to need another label_version_mapper plugin to map Git labels into the versions expected by the generic projects (which won't have a version of core embedded in the version string).
We can't just use the generic one provided by versioncontrol_release since that's [major].[minor].[patch].[extra] and we're aiming for [major].[patch]-[extra]. Hopefully between the existing one in drupalorg_versioncontrol and the generic in versioncontrol_release, it should be fairly easy for someone to figure out how to do this.
Comments
Comment #1
dwwAlthough #1434500: Add project-type-specific settings for label_version_mapper plugin and the original proposal here would perhaps be cleaner, it just occurred to me we could combine them and just further complicate the existing DrupalorgVersioncontrolLabelVersionMapperGit plugin. It's already got the special-case for core. These generic "other" projects would be using the identical mapping. So, maybe it's easier to just hack DrupalorgVersioncontrolLabelVersionMapperGit so that instead of this:
It was something like:
...
Comment #2
drumm