gundalow's meeting titled "Ansible Community Meeting" ended in
#ansible-community
by notifications@fedoraproject.org
Notification time stamped 2020-07-22 19:55:48 UTC
=============================================
#ansible-community: Ansible Community Meeting
=============================================
Meeting started by gundalow at 18:00:04 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/ansible-community/2020-07-22/ansible_co...
.
Meeting summary
---------------
* Agenda https://github.com/ansible/community/issues/539 (gundalow,
18:02:20)
* Release 1.0.0 of community.general and community.network (gundalow,
18:03:14)
* c.general and #c.network need have correctly generated plugin docs
before we release 1.0.0 (gundalow, 18:15:47)
* LINK: https://github.com/ansible-community/antsibull/issues/147
(abadger1999, 18:23:23)
* 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)
* LINK:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/roadmap/RO...
should link to the new ansible (add) roadmap (gundalow, 19:01:49)
* AGREED: `ansible` roadmap will live alongside ansible-base roadmap
(which needs renaming) (gundalow, 19:17:21)
* Module versioning (gundalow, 19:18:36)
* LINK:
http://docs.testing.ansible.com/ansible/2.10/collections/wti/remote/cpm_i...
(samccann, 19:20:52)
* LINK:
https://github.com/wtinetworkgear/wti-collection/blob/master/wti/remote/p...
(felixfontein, 19:30:01)
* LINK:
https://github.com/ansible/community/issues/521#issuecomment-624153545
(felixfontein, 19:43:47)
* ACTION: samccann add to the collection checklist that version_added
should not say 2.10, but should say collection version (samccann,
19:46:48)
Meeting ended at 19:55:48 UTC.
Action Items
------------
* 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
People Present (lines said)
---------------------------
* felixfontein (123)
* gundalow (85)
* samccann (58)
* abadger1999 (57)
* acozine (34)
* cyberpear (24)
* zodbot (14)
* nitzmahone (2)
* gwmngilfen (1)
* baptistemm (1)
* rbergeron (0)
* gregdek (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
https://meetbot.fedoraproject.org/ansible-community/2020-07-22/ansible_co...
--
You received this message due to your preference settings at
https://apps.fedoraproject.org/notifications/fmnmeetingminutes.id.fedorap...