From d13bbe71baf39843a9592f377ab2dd0116da0ac0 Mon Sep 17 00:00:00 2001 From: Maxwell G Date: Sat, 11 Nov 2023 18:58:15 +0000 Subject: [PATCH] ansible-readme.rst: mention the ansible-build-data issue tracker Ref: /~https://github.com/ansible-community/ansible-build-data/pull/322#issuecomment-1806868259 --- changelogs/fragments/554-readme2.yaml | 4 ++++ src/antsibull/data/ansible-readme.rst | 4 ++++ tests/test_data/package-files/7.5.0/README.rst | 4 ++++ tests/test_data/package-files/8.1.0/README.rst | 4 ++++ .../test_data/package-files/force_setup_cfg/8.1.0/README.rst | 4 ++++ 5 files changed, 20 insertions(+) create mode 100644 changelogs/fragments/554-readme2.yaml diff --git a/changelogs/fragments/554-readme2.yaml b/changelogs/fragments/554-readme2.yaml new file mode 100644 index 00000000..4960b814 --- /dev/null +++ b/changelogs/fragments/554-readme2.yaml @@ -0,0 +1,4 @@ +--- +minor_changes: + - "``ansible`` package README - add a link to the ``ansible-build-data`` issue tracker + (/~https://github.com/ansible-community/antsibull/pull/554)." diff --git a/src/antsibull/data/ansible-readme.rst b/src/antsibull/data/ansible-readme.rst index 44d46b58..42ac8e3b 100644 --- a/src/antsibull/data/ansible-readme.rst +++ b/src/antsibull/data/ansible-readme.rst @@ -56,6 +56,10 @@ Issues with plugins and modules in the Ansible package should be reported on the individual collection's issue tracker. Issues with ``ansible-core`` should be reported on the `ansible-core issue tracker `_. +Issues with the ``ansible`` package build process or serious bugs or +vulnerabilities in a collection that are not addressed after opening an issue +in the collection's issue tracker should be reported on +`ansible-build-data's issue tracker `_. Refer to the `Communication page `_ for a diff --git a/tests/test_data/package-files/7.5.0/README.rst b/tests/test_data/package-files/7.5.0/README.rst index 44d46b58..42ac8e3b 100644 --- a/tests/test_data/package-files/7.5.0/README.rst +++ b/tests/test_data/package-files/7.5.0/README.rst @@ -56,6 +56,10 @@ Issues with plugins and modules in the Ansible package should be reported on the individual collection's issue tracker. Issues with ``ansible-core`` should be reported on the `ansible-core issue tracker `_. +Issues with the ``ansible`` package build process or serious bugs or +vulnerabilities in a collection that are not addressed after opening an issue +in the collection's issue tracker should be reported on +`ansible-build-data's issue tracker `_. Refer to the `Communication page `_ for a diff --git a/tests/test_data/package-files/8.1.0/README.rst b/tests/test_data/package-files/8.1.0/README.rst index 44d46b58..42ac8e3b 100644 --- a/tests/test_data/package-files/8.1.0/README.rst +++ b/tests/test_data/package-files/8.1.0/README.rst @@ -56,6 +56,10 @@ Issues with plugins and modules in the Ansible package should be reported on the individual collection's issue tracker. Issues with ``ansible-core`` should be reported on the `ansible-core issue tracker `_. +Issues with the ``ansible`` package build process or serious bugs or +vulnerabilities in a collection that are not addressed after opening an issue +in the collection's issue tracker should be reported on +`ansible-build-data's issue tracker `_. Refer to the `Communication page `_ for a diff --git a/tests/test_data/package-files/force_setup_cfg/8.1.0/README.rst b/tests/test_data/package-files/force_setup_cfg/8.1.0/README.rst index 44d46b58..42ac8e3b 100644 --- a/tests/test_data/package-files/force_setup_cfg/8.1.0/README.rst +++ b/tests/test_data/package-files/force_setup_cfg/8.1.0/README.rst @@ -56,6 +56,10 @@ Issues with plugins and modules in the Ansible package should be reported on the individual collection's issue tracker. Issues with ``ansible-core`` should be reported on the `ansible-core issue tracker `_. +Issues with the ``ansible`` package build process or serious bugs or +vulnerabilities in a collection that are not addressed after opening an issue +in the collection's issue tracker should be reported on +`ansible-build-data's issue tracker `_. Refer to the `Communication page `_ for a