18:00:04 <felixfontein> #startmeeting Ansible Community Meeting
18:00:04 <zodbot> Meeting started Wed May 24 18:00:04 2023 UTC.
18:00:04 <zodbot> This meeting is logged and archived in a public location.
18:00:04 <zodbot> The chair is felixfontein. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
18:00:04 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:04 <zodbot> The meeting name has been set to 'ansible_community_meeting'
18:00:04 <felixfontein> #topic Agenda https://github.com/ansible/community/issues/679
18:00:09 <felixfontein> Landrash[m], acozine, andersson007_, anwesha, ascherbaum, baptistemm, bcoca, briantist, cidrblock, cyberpear, cybette, dericcrago, dmsimard, felixfontein, geerlingguy, gotmax, gundalow, gwmngilfen, ikhan_, jillr, jtanner, lmodemal, mariolenz[m], markuman, maxamillion, misc, nitzmahone, oranod, resmo, russoz, samccann, thaumos, wbentley15[m], zbr: The Ansible community meeting is starting
18:00:15 <felixfontein> now!
18:00:17 <felixfontein> The ping list is stored at https://kutt.it/meeting-people. Feel free to add or remove yourself.
18:00:20 <felixfontein> #info Agenda: https://github.com/ansible/community/issues/679 / Topics: https://github.com/ansible-community/community-topics
18:00:23 <felixfontein> #topic Updates
18:01:04 <felixfontein> anyone around today? :)
18:01:09 <bcoca> no
18:01:34 <felixfontein> #chair bcoca
18:01:34 <zodbot> Current chairs: bcoca felixfontein
18:01:36 <felixfontein> found one! \o/
18:01:46 <bcoca> dammit, it's a trap!
18:01:48 <felixfontein> #info Ansible 7.6.0 has been released (https://groups.google.com/g/ansible-project/c/PAbzRgS1xok)
18:02:27 <felixfontein> #info Ansible 8.0.0rc1 has been released (https://groups.google.com/g/ansible-project/c/lHMcTcvmaWk). If no blockers are found until the end of this week, 8.0.0 will be released next week (https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_8.html)
18:02:40 <oranod> o/
18:02:43 <oranod> hello
18:02:46 <felixfontein> #chair oranod
18:02:46 <zodbot> Current chairs: bcoca felixfontein oranod
18:03:34 <gotmax23> .hi
18:03:36 <zodbot> gotmax23: gotmax23 'Maxwell G' <maxwell@gtmx.me>
18:03:40 * gotmax23 is multitasking with lunch
18:03:48 <felixfontein> #chair gotmax23
18:03:48 <zodbot> Current chairs: bcoca felixfontein gotmax23 oranod
18:03:51 <felixfontein> enjoy lunch :)
18:06:10 <felixfontein> #info While working on the releases we found several serious collection requirement violations: two violations concern breaking changes in minor releases, and one is about a dependency on ansible.netcommon < 5.0.0, while Ansible 8 will contain ansible.netcommon 5.x.y
18:06:23 <felixfontein> details can be found in the tracking issue: https://github.com/ansible-community/ansible-build-data/issues/223
18:06:34 <gotmax23> yeah :(
18:07:32 <gotmax23> dellemc.enterprise_sonic has both depclosure errors and semver violations, which is unfortunate
18:07:42 <felixfontein> IMO these are some of the worst requirement violations; unexpected breaking changes in minor/patch Ansible releases are bad, and broken dependencies are also bad
18:08:20 <gotmax23> yeah, I agree.
18:08:35 <gotmax23> We have automated tests for tagging violations and depclosure errors but not semver violations
18:08:47 <felixfontein> dellemc.enterprise_sonic 2.1.0 restricted the dependency on ansible.netcommon, while 2.0.0 didn't, so we now pin to 2.0.0 - unfortunately 2.0.0 doesn't work with ansible.netcommon 5.x.y, that's apparently why the dependency restriction was added
18:08:53 <gotmax23> I wonder if we should have antsibull print a warning if it finds any major change entries in collection changelogs
18:09:17 <felixfontein> it's a bit complex since there are a few collections that report all features as "major changes"...
18:10:04 <gotmax23> hmm
18:10:31 <felixfontein> there are also edge cases where breaking changes can be acceptable (mainly in the context of security issues, but maybe there are also other examples), but the breaking changes done by these two collections don't seem to fall in that category
18:10:43 <gotmax23> right
18:11:05 <gotmax23> I guess manually scrolling through the changelog diff in release PRs isn't soo bad
18:11:32 <felixfontein> yeah, I usually look in particular at the porting guide diff since breaking and major changes show up in there as well (next to deprecations)
18:14:24 <gotmax23> Do we have other topics or should we move to open floor?
18:14:40 <gotmax23> I think there's still the Ansible 9 Roadmap to discuss
18:14:51 <felixfontein> #topic Ansible 9 roadmap
18:15:00 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:15:10 <felixfontein> #link https://github.com/ansible/ansible/pull/80851
18:16:08 * gotmax23 needs to formally review that
18:16:13 <felixfontein> the changes suggested by Don look good IMO
18:16:25 <felixfontein> basically everything was a copy'n'paste from the Ansible 8 roadmap, with dates adjusted
18:18:09 <gotmax23> It looks pretty much like the last schedule to me
18:19:16 <gotmax23> I think the three weeks between the core GA and the community package GA and doing the day after new ansible-core releases has worked well for us
18:20:22 <felixfontein> it's only two weeks now, not three :)
18:20:35 <felixfontein> it can be up to three if we notice that we need another RC
18:20:56 <felixfontein> in any case, I agree that it worked well, and IMO we should keep doing it this way
18:22:14 <gotmax23> Right
18:22:59 <felixfontein> I added some more suggestions, if nobody objects I'll merge them
18:23:10 <felixfontein> should we start a formal vote on this at the beginning of next week?
18:23:20 <gotmax23> SGTM
18:24:28 <felixfontein> cool!
18:24:31 <felixfontein> #topic open floor
18:26:04 <gotmax23> I followed up on https://github.com/ansible-community/ansible-build-data/pull/227.
18:27:25 <gotmax23> I think it's in a mergable state, but i"ll wait for anwesha to get back from Pycon and take another look.
18:29:58 <gotmax23> We're also working on fixing the antsibull bug with version constraints that came up in last release (https://github.com/ansible-community/antsibull/pull/533)
18:30:01 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:32:04 <felixfontein> fortunately that bug shouldn't happen again until Ansible 9.0.0rc1 (or 9.0.0b2 if that would be created), so there is no hurry to get it fixed... :)
18:32:56 <gotmax23> Right. We only use --feature-frozen ~twice a year :).
18:33:30 <felixfontein> yep :)
18:34:27 <gotmax23> We can probably end in a couple minutes if there's no other topics. There's Summit and Fest and a bunch of other things going on :).
18:34:52 <felixfontein> sounds good to me
18:42:16 <felixfontein> #endmeeting