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.

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

update changelog fragment guidance with examples #77040

Merged
merged 3 commits into from
Feb 22, 2022

Conversation

samccann
Copy link
Contributor

SUMMARY

Community wanted better guidance on how to write good changelog fragments. This PR
Implements ansible-community/community-topics#64 where this was decided on.

There are two guides now - one for core and one for collections, thus the repeated content in this PR.

ISSUE TYPE
  • Docs Pull Request
COMPONENT NAME

docs/docsite/rst/community/collection_development_process.rst
docs/docsite/rst/community/development_process.rst

ADDITIONAL INFORMATION

@ansibot ansibot added affects_2.13 core_review In order to be merged, this PR must follow the core review workflow. docs This issue/PR relates to or includes documentation. docs_only All changes are to files within the docs/docsite/ directory docsite This issue/PR relates to the documentation website. has_issue needs_triage Needs a first human triage before being processed. support:core This issue/PR relates to code supported by the Ansible Engineering Team. labels Feb 16, 2022
@nitzmahone nitzmahone removed the needs_triage Needs a first human triage before being processed. label Feb 17, 2022
Copy link
Contributor

@acozine acozine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great! I've added some suggestions to make it even better.

Co-authored-by: Alicia Cozine <879121+acozine@users.noreply.github.com>
@samccann samccann merged commit 30d1a93 into ansible:devel Feb 22, 2022
@samccann samccann deleted the changelog-instructions branch February 22, 2022 19:02
.. code-block:: yaml

breaking_changes:
- ec2_instance - instance wait for state behavior has changed. If plays require the old behavior of waiting for the instance monitoring status to become OK when launching a new instance, the action will need to specify ``state: started`` (https://github.com/ansible-collections/amazon.aws/pull/481).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This snippet seems inconsistent with the paragraph above. The explanation says to use the present tense but the example has a mixture and starts with the past tense.
Should the guidance be made clearer? Does the "present tense" request imply an imperative mood?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry about that, updated in #77138

@ansible ansible locked and limited conversation to collaborators Mar 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.13 core_review In order to be merged, this PR must follow the core review workflow. docs_only All changes are to files within the docs/docsite/ directory docs This issue/PR relates to or includes documentation. docsite This issue/PR relates to the documentation website. has_issue support:core This issue/PR relates to code supported by the Ansible Engineering Team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants