slawekjaranowski opened a new issue, #1748: URL: https://github.com/apache/maven-site/issues/1748
The shared ATR announce template `content/resources/atr/templates/announce_release_template.txt` builds the release notes link as: https://github.com/apache/{{PROJECT_KEY}}/releases/tag/{{PROJECT_KEY}}-{{VERSION}} This works for most Maven projects, where the release tag is `<ATR project key>-<version>`. Some repositories use a different tag naming, so the link in the announcement email points to a non-existing page. Affected projects (ATR key = repository name): | Repository | Tag format | Release page example | |---|---|---| | [maven-apache-parent](https://github.com/apache/maven-apache-parent/tags) | `apache-<v>` | https://github.com/apache/maven-apache-parent/releases/tag/apache-40 | | [maven-apache-resources](https://github.com/apache/maven-apache-resources/tags) | `apache-resource-bundles-<v>` | https://github.com/apache/maven-apache-resources/releases/tag/apache-resource-bundles-1.8 | | [maven-archetypes](https://github.com/apache/maven-archetypes/tags) | `maven-archetype-bundles-<v>` | https://github.com/apache/maven-archetypes/releases/tag/maven-archetype-bundles-1.5 | | [maven-doxia](https://github.com/apache/maven-doxia/tags) | `doxia-<v>` | https://github.com/apache/maven-doxia/releases/tag/doxia-2.2.0 | | [maven-doxia-converter](https://github.com/apache/maven-doxia-converter/tags) | `doxia-converter-<v>` | https://github.com/apache/maven-doxia-converter/releases/tag/doxia-converter-1.3 | | [maven-doxia-sitetools](https://github.com/apache/maven-doxia-sitetools/tags) | `doxia-sitetools-<v>` | https://github.com/apache/maven-doxia-sitetools/releases/tag/doxia-sitetools-2.1.0 | | [maven-enforcer](https://github.com/apache/maven-enforcer/tags) | `enforcer-<v>` | https://github.com/apache/maven-enforcer/releases/tag/enforcer-3.7.0 | | [maven-executor](https://github.com/apache/maven-executor/tags) | `executor-<v>` | https://github.com/apache/maven-executor/releases/tag/executor-1.0.0 | | [maven-file-management](https://github.com/apache/maven-file-management/tags) | `file-management-<v>` | https://github.com/apache/maven-file-management/releases/tag/file-management-3.1.0 | | [maven-jxr](https://github.com/apache/maven-jxr/tags) | `jxr-<v>` | https://github.com/apache/maven-jxr/releases/tag/jxr-3.6.0 | | [maven-mvnd](https://github.com/apache/maven-mvnd/tags) | `<v>` (no prefix) | https://github.com/apache/maven-mvnd/releases/tag/1.0.6 | | [maven-surefire](https://github.com/apache/maven-surefire/tags) | `surefire-<v>` | https://github.com/apache/maven-surefire/releases/tag/surefire-3.6.1 | | [maven-wagon](https://github.com/apache/maven-wagon/tags) | `wagon-<v>` | https://github.com/apache/maven-wagon/releases/tag/wagon-3.5.3 | ### Proposed solutions **1. Generic link in the shared template** Replace the tag-specific link with the repository releases page: https://github.com/apache/{{PROJECT_KEY}}/releases Pros: one change, works for every project, no per-project configuration. Cons: the announcement no longer points directly to the notes of the announced version. **2. Project-specific announce template for affected projects** Keep the shared template as is, and configure an own announce template in the `project:` section of `.asf.yaml` for the projects listed above, with the correct tag format, e.g. for maven-enforcer: https://github.com/apache/maven-enforcer/releases/tag/enforcer-{{VERSION}} Pros: direct link to the release notes of the announced version for all projects. Cons: 13 copies of the template to maintain; changes to the shared template must be repeated there. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
