Ansible 3.0.0 beta 1 has been released(felixfontein,
19:01:37)
Several new collections have been included in
Ansible 3: t_systems_mms.icinga_director, sensu.sensu_go,
community.sops, inspur.sm, dellemc.openmanage, and
ansible.utils!(felixfontein,
19:01:37)
AGREED: We approved
the Ansible-4.0 schedule: PR for docs.a.c:
https://github.com/ansible/ansible/pull/73465 (document with
background info: https://hackmd.io/y7BBcweNR3aRVLuMbKkDxw)(felixfontein,
19:25:39)
community.network: who wants to take over maintenance / releasing?(felixfontein, 19:26:04)
ACTION: dmsimard to
talk about community.network maintenance at the next network working
group meeting(dmsimard,
19:31:35)
Proposal for Python version support for collections (https://github.com/ansible-collections/overview/pull/151)(felixfontein, 19:35:00)
AGREED: Collections
do not need to support Python 2.6 and Python 3.5 if they chose not
to. This must be well documented though (for every plugin/module,
and in the collection README). (many +1, one -1)(felixfontein,
20:06:19)
AGREED: Add 'We
recommend that collections try to support 2.6 and 3.5 as well. Not
supporting Python 2.6 means that you are dropping support for RHEL6,
which has extended support until 2024. Not supporting Python 3.5
means that Python 2.7 has to be installed on Ubuntu Xenial (16.04),
and that you have to support Python 2.7. Also note that dropping
support for a Python version for an(felixfontein,
20:21:47)
AGREED: Change the
'recommend' to 'SHOULD' in the above, i.e. 'Collections SHOULD try
to support 2.6 and 3.5 as well.' (1 x -1, 1 x +0, 4 x +1)(felixfontein,
20:32:21)
Require that collection releases are tagged in the git repo(felixfontein, 20:34:05)
AGREED: 'Every
collection must have a public SCM repository, and releases of the
collection must be tagged in this repository.'(felixfontein,
20:52:18)