- The 2.3 Ansible Core is just a little different than the past two major releases we've done. In addition to feature work, we're using part of the time for this release to reduce some of our backlog in other areas than pure development.
- *Administration:* Clean up our GitHub repos and move to one repo so that contributions, tickets, submissions, etc are centralized and easier for both the community and the Core Team to manage.
- *Metadata:* Move to a Metadata based system for modules. This has been discussed here: https://github.com/ansible/proposals/blob/master/modules-management.md
- *Metadata:* Move to a Metadata based system for modules. This has been discussed here: https://github.com/ansible/proposals/blob/master/modules-management.md
- *Documentation:* We're aware that Docs have issues. Scott Butler, aka Dharmabumstead will be leading the charge on how he and we as a community can clean them up.
- *Backlog & Stability:* We're spending some of the cycles for 2.3 trying to reduce our ticket/PR backlog, and clean up some particular areas of the project that the community has expressed particular frustrations about.
- *Python 3:* The community and Toshio have done TONS of work getting Python 3 working. Still more to go...
@ -25,16 +25,16 @@ Target: February/March 2017
- **Metadata**
- Add metadata to the modules we ship
- Add metadata to the modules we ship (done)
- Write code to use metadata in docs
- If needed for python2/3 write code to use metadata in module_common or pluginloader
- **Documentation**
- Update developing_modules
- Update developing_modules (in progress, will continue in 2.4)
- Set up rst skeleton for module_utils docs.
- Plugin development docs
- Speed up `make webdocs` https://github.com/ansible/ansible/issues/17406 [done]
- Speed up `make webdocs` https://github.com/ansible/ansible/issues/17406 (done)
John R Barker
8 years ago
committed by