docs: adds Ansible 5 roadmap #75075
docs: adds Ansible 5 roadmap #75075
Conversation
ansibot
added
affects_2.12
docs
| Ansible project 5.0 | ||
| =================== | ||
|
|
||
| This release schedule includes dates for the `ansible <https://pypi.org/project/ansible/>`_ package, with a few dates for the `ansible-core <https://pypi.org/project/ansible-core/>`_ package as well. All dates are subject to change. See :ref:`base_roadmap_2_12` for the most recent updates on ``ansible-core``. |
There was a problem hiding this comment.
The draft included dates from ansible-core but they seem to have been removed from this proposal. We should adjust the phrasing or include the dates back here for easy reference.
There was a problem hiding this comment.
I copied this file from the Ansible 4 roadmap, which didn't have any of the core dates in it. I'm happy to add those if we want to maintain them going forward, but they do appear on the 2.12 roadmap, which is linked here in the first paragraph.
There was a problem hiding this comment.
Addressed in c740157.
There was a problem hiding this comment.
Is it an issue to include ansible-core dates on the ansible community package roadmap ? I'm mostly thinking about if core changes their roadmap, this one will become out of sync.
There was a problem hiding this comment.
Well, if the core dates slip, the community package dates will slip too, right? So we'd need to update this page anyway.
There was a problem hiding this comment.
Yes, that's very likely.
ansibot
added
core_review
Co-authored-by: Sandra McCann <samccann@redhat.com> Co-authored-by: David Moreau Simard <moi@dmsimard.com> Co-authored-by: Felix Fontein <felix@fontein.de>
mkrizek
removed
the
needs_triage
Co-authored-by: Felix Fontein <felix@fontein.de>
ansibot
added
needs_ci
SUMMARY
Part of #74576.
Details the schedule for the release of Ansible 5.
ISSUE TYPE
COMPONENT NAME
docs.ansible.com
ADDITIONAL INFORMATION
Schedule copied from https://hackmd.io/y7BBcweNR3aRVLuMbKkDxw#Proposed-Schedule-for-Ansible-50, which was affirmed at the community working group meeting on June 16.