one idea - we would have two options for
collection owners - 1. use our tool, or 2. use your own solution and
provide us with a file that looks like <proposal>
https://gist.github.com/felixfontein/d15112c7a866e8806d7e9f9ea4085cfa(samccann,
15:42:13)
this would require (1) core team has to get the
ansible/ansible changelog generator to output the new format. (2)
the community team would have to write code for the acd changelog
generator to consume the new format(samccann,
15:42:30)
another idea - we mandate one tool and
integrate that tool's output with core's changelog (aka collections
in ACD would not have a choice but must use this tool)(samccann,
15:45:10)
- third idea - we link to peoples disparate
change logs (least work, but doesn't give comprehensive view of
changes, just a bunch of links users have to follow)(samccann,
15:46:00)
- fourth idea - people write an input =>
input transform + metadata of what input fragments are needed for
the next release. - similar to first proposal, but there are
individual fragments instead of a container(samccann,
15:46:58)
fifth idea - we handle ACD like a linux distro
- changelogs would be links. however, there would be a common
release notes that individual components could contribute things
they considered major enough to be worthy of that.(samccann,
15:48:12)