mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
Updated for 2.4 Roadmap
- Added in 2.4 roadmap page - Updated top-level Roadmap to reflect new page
This commit is contained in:
parent
470d1e3aea
commit
cf83a235d5
2 changed files with 44 additions and 6 deletions
13
ROADMAP.rst
13
ROADMAP.rst
|
@ -1,26 +1,27 @@
|
|||
*******************************
|
||||
Roadmap For Ansible by Red Hat
|
||||
*******************************
|
||||
This document is now the location for published Ansible Core roadmaps.
|
||||
This document is now the location for published Ansible Core roadmaps.
|
||||
|
||||
The roadmap will be updated by version. Based on team and community feedback, an initial roadmap will be published for a major or minor version (2.0, 2.1). Subminor versions will generally not have roadmaps published.
|
||||
|
||||
2.1 was the first time Ansible has published this and asked for feedback in this manner. So feedback on the roadmap and the new process is quite welcome. The team is aiming for further transparency and better inclusion of both community desires and submissions.
|
||||
2.1 was the first time Ansible has published this and asked for feedback in this manner. So feedback on the roadmap and the new process is quite welcome. The team is aiming for further transparency and better inclusion of both community desires and submissions.
|
||||
|
||||
These roadmaps are the team's *best guess* roadmaps based on the Ansible team's experience and are also based on requests and feedback from the community. There are things that may not make it on due to time constraints, lack of community maintainers, etc. And there may be things that got missed, so each roadmap is published both as an idea of what is upcoming in Ansible, and as a medium for seeking further feedback from the community. Here are the good places for you to submit feedback:
|
||||
|
||||
- Ansible's google-group: ansible-devel
|
||||
- Ansible Fest conferences.
|
||||
- Ansible Fest conferences.
|
||||
- IRC freenode channel: #ansible-devel (this one may have things lost in lots of conversation, so a caution).
|
||||
|
||||
=======================================
|
||||
Current 2.3 Roadmap is open for comment
|
||||
Current 2.4 Roadmap is open for comment
|
||||
=======================================
|
||||
We are currently trying to finalize the 2.3 Roadmap, targeted for January delivery. We are seeking community feedback for 2.3. That document is here:
|
||||
- `2.3 Roadmap Document <docsite/rst/roadmap/ROADMAP_2_3.rst>`_
|
||||
We are starting to build the 2.4 Roadmap, targeted for June/July delivery. We are seeking community feedback! That document is here:
|
||||
- `2.4 Roadmap Document <docsite/rst/roadmap/ROADMAP_2_4.rst>`_
|
||||
|
||||
|
||||
|
||||
**Old Roadmaps are found here:**
|
||||
- `2.3 Roadmap Document <docsite/rst/roadmap/ROADMAP_2_3.rst>`_
|
||||
- `2.2 Roadmap Document <docsite/rst/roadmap/ROADMAP_2_2.rst>`_
|
||||
- `2.1 Roadmap Document <docsite/rst/roadmap/ROADMAP_2_1.rst>`_
|
||||
|
|
37
docsite/rst/roadmap/ROADMAP_2_4.rst
Normal file
37
docsite/rst/roadmap/ROADMAP_2_4.rst
Normal file
|
@ -0,0 +1,37 @@
|
|||
Ansible by Red Hat, Core 2.4
|
||||
============================
|
||||
|
||||
**Target Delivery: June/July 2017**
|
||||
|
||||
This is meant to be a living document, and is by no means **FINAL** until
|
||||
stated otherwise in the document.
|
||||
|
||||
- **Ansible-Config**
|
||||
- New yaml format for config
|
||||
- Extend the ability of the current config system by adding creating an ansible-config command and add the following:
|
||||
|
||||
- Dump existing config settings
|
||||
- Update / write a config entry
|
||||
- Show available options (ini entry, yaml, env var, etc)
|
||||
|
||||
- Proposal found in ansible/proposals issue `#35 <https://github.com/ansible/proposals/issues/35>`_.
|
||||
- Initial PR of code found in ansible/ansible PR `#12797 <https://github.com/ansible/ansible/pull/12797>`_.
|
||||
|
||||
- **Inventory Overhaul**
|
||||
|
||||
- Current inventory is overtly complex, non modular and mostly still a legacy from inception. We also want to add a common set of features to most inventory sources but are hampered by the current code base.
|
||||
- Proposal found in ansible/proposals issue `#41 <https://github.com/ansible/proposals/issues/41>`_.
|
||||
|
||||
- **Facts Refreshening**
|
||||
|
||||
- Make setup.py/facts more pluggable
|
||||
- Fact gathering policy finer grained
|
||||
|
||||
- **Cloud Provider Support**
|
||||
|
||||
- Focus on pull requests for various modules
|
||||
- Triage existing merges
|
||||
|
||||
- **Contributor Quality of Life**
|
||||
|
||||
- More bot improvements!
|
Loading…
Reference in a new issue