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

changelog and porting guide for 2.17 missing info about Py2.7 and Py3.6 support removal #83054

Closed
1 task done
sivel opened this issue Apr 16, 2024 · 3 comments
Closed
1 task done
Labels
has_pr This issue has an associated PR.

Comments

@sivel
Copy link
Member

sivel commented Apr 16, 2024

Summary

The 2.17 changelog and porting guide are missing explicit mentions of removing python 2.7 and 3.6 support for target execution.

Issue Type

Documentation Report

Component Name

changelogs/fragments/

Ansible Version

$ ansible --version

Configuration

# if using a version older than ansible-core 2.12 you should omit the '-t all'
$ ansible-config dump --only-changed -t all

OS / Environment

NA

Additional Information

NA

Code of Conduct

  • I agree to follow the Ansible Code of Conduct
@ansibot
Copy link
Contributor

ansibot commented Apr 16, 2024

Files identified in the description:

If these files are incorrect, please update the component name section of the description or use the component bot command.

@ansibot ansibot added the needs_triage Needs a first human triage before being processed. label Apr 16, 2024
@felixfontein
Copy link
Contributor

The porting guide right now is completely empty, except some default filler text :) There might be more things that should be mentioned there, next to dropping support for Python 2.7 and 3.6 on remotes.

@oraNod
Copy link
Contributor

oraNod commented Apr 17, 2024

Thanks for creating the issue @sivel and @mkrizek for the docs PR. Think we can close this as done now. Cheers.

@sivel sivel closed this as completed Apr 17, 2024
@sivel sivel removed the needs_triage Needs a first human triage before being processed. label Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has_pr This issue has an associated PR.
Projects
None yet
Development

No branches or pull requests

4 participants