AGREED: c.g and c.n
1.0.0 will be released on Friday, July 31st(felixfontein,
18:36:26)
ACTION: felixfontein
write instructions for how to do major release (and maybe also minor
/ patch releases) for c.g and c.n(felixfontein,
18:36:44)
ACTION: felixfontein
announce 1.0.0 date in repo issues(felixfontein,
18:36:54)
ACTION: samcann
mention collection docs, 1) what to check for 2) where to report
issues 3) that we know c.general is broken 4) anything else on
https://github.com/ansible-collections/overview/issues/45 (changes
impacting contributors)(samccann,
18:38:49)
ACTION: abadger do
not release a new alpha on Thursday July 30th, but wait until Friday
July 31st(felixfontein,
18:38:56)
ACTION: samccann
acozine republish 2.10 on Fri July 31 (after c.g release an ansible
alpha release)(samccann,
18:39:53)
antsibull-docs CLI change: Rename
--ansible-base-cache to --ansible-base-source(abadger1999,
18:43:52)
antsibull-build CLI change: Remove the
redundant build- prefix from antsibull-build subcommands(abadger1999,
18:44:16)
both antsibull-docs and antsibull-build file
format change: Renaming "acd_" fields to "ansible_" and renaming
default filenames in the same way.(abadger1999,
18:44:59)
the changes that affect antsibull-docs will
operate with backwards compatibility for at least a few weeks
[probably until after 2.10.0 is released](abadger1999,
18:45:55)
ACTION: abadger to
get clarification from rbergeron about some of th edates and
milestones(abadger1999,
18:52:39)
Question1: Which freeze date determines the
major version of collections that will go into Ansible-2.10
(abadger1999 suggests beta freeze date)?(abadger1999,
18:54:02)
Question2: Will either new minor releases or
patch releases of collections be allowed between RC1 and GA of
2.10.0 (abadger1999 suggests no, but might need ask to adjust the
rc->GA dates in that case)?(abadger1999,
18:55:30)
felixfontein write instructions for how to do major release (and maybe also minor / patch releases) for c.g and c.n
felixfontein announce 1.0.0 date in repo issues
samcann mention collection docs, 1) what to check for 2) where to report issues 3) that we know c.general is broken 4) anything else on https://github.com/ansible-collections/overview/issues/45 (changes impacting contributors)
abadger do not release a new alpha on Thursday July 30th, but wait until Friday July 31st
samccann acozine republish 2.10 on Fri July 31 (after c.g release an ansible alpha release)
abadger to get clarification from rbergeron about some of th edates and milestones
samccann add to the collection checklist that version_added should not say 2.10, but should say collection version
Action items, by person
acozine
samccann acozine republish 2.10 on Fri July 31 (after c.g release an ansible alpha release)
felixfontein
felixfontein write instructions for how to do major release (and maybe also minor / patch releases) for c.g and c.n
felixfontein announce 1.0.0 date in repo issues
rbergeron
abadger to get clarification from rbergeron about some of th edates and milestones
samccann
samccann acozine republish 2.10 on Fri July 31 (after c.g release an ansible alpha release)
samccann add to the collection checklist that version_added should not say 2.10, but should say collection version
UNASSIGNED
samcann mention collection docs, 1) what to check for 2) where to report issues 3) that we know c.general is broken 4) anything else on https://github.com/ansible-collections/overview/issues/45 (changes impacting contributors)
abadger do not release a new alpha on Thursday July 30th, but wait until Friday July 31st