Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs/polices.md: refine tagging violation issue template #315

Merged
merged 2 commits into from
Nov 7, 2023
Merged

docs/polices.md: refine tagging violation issue template #315

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
840d7e9
docs/policies.md: unwrap tagging violation issue template
gotmax23 Nov 6, 2023
ec5e3b3
docs/policies.md: fix extra word in issue template
gotmax23 Nov 6, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 2 additions & 9 deletions docs/policies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,9 +99,7 @@ In case of violations, the release manager must preform the following steps:
The following issue template can be used:

``` markdown
Hi! As part of the ansible community package release process,
we've determined that version {VERSION} of {COLLECTION} was released to
Ansible Galaxy but not properly tagged in this Git repository.
Hi! As part of the ansible community package release process, we've determined that version {VERSION} of {COLLECTION} was released to Ansible Galaxy but not properly tagged in this Git repository.
This violates the [repository management][1] section of the Collection Requirements:

[1]: https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_requirements.html#repository-management
Expand All @@ -110,12 +108,7 @@ In case of violations, the release manager must preform the following steps:
>
> Additionally, collection artifacts released to Galaxy MUST be built from the sources that are tagged in the collection's git repository as that release. Any changes made during the build process MUST be clearly documented so the collection artifact can be reproduced.

Until this issue is fixed,
ansible package releases will contain {OLD VERSION},
the previous version of this collection that was properly tagged.
If the collection maintainers do not respond to this issue within a
reasonable a amount of time,
the collection is subject to [Removal from ansible][2].
Until this issue is fixed, ansible package releases will contain {OLD VERSION}, the previous version of this collection that was properly tagged. If the collection maintainers do not respond to this issue within a reasonable amount of time, the collection is subject to [Removal from ansible][2].

[2]: https://github.com/ansible-collections/overview/blob/main/removal_from_ansible.rst#collections-not-satisfying-the-collection-requirements

Expand Down