Ansible-maintained content team considering
reno with added work to produce the changelog.yml that felix's work
requires.(samccann,
14:41:29)
felixfontein wrote up a spec for the
changelog.yaml format
(https://github.com/ansible/ansible/blob/devel/packaging/release/changelogs/changelog.py)
and added a linter for changelog.yaml files to the generator(samccann,
14:43:28)
felixfontein also prepared a WIP PR to replace
ansible's changelog generator with it:
https://github.com/ansible/ansible/pull/69313(samccann,
14:46:38)
The collection downloading and generation of
rst from those collection files will live in ansibulled:
https://github.com/ansible-community/ansibulled/pull/5(samccann,
15:04:13)
The idea is that this will be usable for both
the docs pipeline and external collection authors who want to build
docs for just their collections.(samccann,
15:04:46)
new collections pipeline will be split into two
parts, the ansibulled part mentioned above, which generates rST from
plugin docstrings, and the Sphinx (rST-to-HTML) part(acozine,
15:20:36)
collections owners can use ansibulled-docs to
generation rST from their plugin docstrings(acozine,
15:21:34)
AGREED: would be good
if ansibulled-docs also outputs index.rst files. Will be handy
if/when scenario guides are moved into collections /docs folder and
pulled back to docs.ansible.com(samccann,
15:24:32)
supported_by metadata seems to no longer serve
a purpose. TBD on whether collection owners/core still want status
field in the metadata (stable vs preview etc)(samccann,
15:45:43)
in summary - ansible-base is phasing out
ANSIBLE_METADATA entirely, collections 'may' still want to use the
status field but we need to followup to see if that's true(samccann,
15:48:22)
collection meta/routing.yml should be the
source of truth for deprecation/removed and we can move any other
status needs into an optional DOCUMENTATION field(samccann,
15:51:16)
consider ignoring ANSIBLE_METADATA entirely
when building collection docs(samccann,
16:05:54)