19:00:00 #startmeeting Ansible Core Public IRC Meeting 19:00:00 Meeting started Tue Feb 2 19:00:00 2021 UTC. 19:00:00 This meeting is logged and archived in a public location. 19:00:00 The chair is jborean93. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:00 The meeting name has been set to 'ansible_core_public_irc_meeting' 19:00:05 \o 19:00:05 bam 19:00:22 #chair nitzmahone 19:00:22 Current chairs: jborean93 nitzmahone 19:00:30 hi! 19:00:31 #info https://github.com/ansible/community/issues/585 19:00:43 * shertel waves 19:00:45 Hey all 19:01:11 * mattclay waves 19:01:55 Looks like there is nothing on the agenda itself so we will go straight to the open floor 19:02:00 #topic open floor 19:02:00 * bcoca waves 19:02:41 is feature freeze still planned for February 12th? 19:02:55 yes 19:03:01 good :) 19:03:10 no .. i got a few things that wont make it 19:03:14 :-( 19:03:16 same :( 19:03:26 Only thing for me is if folks have selinux-enabled machines or use apt/yum/dnf, please try out https://github.com/ansible/ansible/pull/73423 with localhost under a Python 3.8+ controller (or by forcing your remote Python to something else) and let me know if you hit any problems... 19:03:31 c'est la vie 19:03:43 hmm, out of curiosity, what is not going to make it? 19:03:52 rue la vie 19:04:03 test/filter docs for one 19:04:12 ah. yeah, that would have been nice :/ 19:04:21 is there something to try out already? 19:04:31 many things .. that is problem, too many formats 19:06:48 oh well, we have 2.12 to look forward too and over estimate our work :) 19:06:49 felixfontein module_defaults action groups won't make it, most likely. It wasn't included in the roadmap and I'm still trying to get galaxy features done. 19:07:17 split controller/remote wont make it before freeze 19:07:20 shertel: ah, too bad 19:07:29 mattclay: also too bad 19:07:33 controller side argspec 19:07:34 and still no way to move freeze? :) 19:07:38 mergable yaml configs 19:07:43 platform 19:07:49 is anything interesting actually in before freeze? ;) (just joking) 19:08:04 ^ what nitz linked 19:08:06 * resmo waves 19:08:16 We migrated to Azure Pipelines. :) 19:08:29 felixfontein: the galaxy dep resolver work is in and fantastic :-) 19:08:30 * resmo .oO(pff) 19:08:48 our galaxy, not the galaxy 19:08:54 yes, galaxy cli 19:09:09 Which is good, since Shippable is shutting down on May 3rd. 19:09:09 * bcoca needs a constelation now 19:09:19 oh, they actually have a date now? 19:09:27 shertel: indeed! 19:09:38 (beyond Real Soon Now) 19:09:39 Yeah, gundalow posted it here: https://github.com/ansible-collections/overview/issues/124#issuecomment-771060350 19:09:42 I heard about a date earlier today, it's probably new 19:10:25 so ... the day after 19:10:27 It's a lot farther out than I expected. I had previously been told it would be the end of 2020. 19:11:23 they probably happy to not have us 'load testing' them constantly 19:11:42 I heard that too... but I guess it's good for us, since there are still some collections to migrate 19:14:07 hopefully it's not too many left to go 19:14:59 I stopped counting, since all that I actively work with have migrated :) 19:15:20 well, community.general and community.network still have shippable (for sanity tests) because the collection bot hasn't been updated yet to read results from AZP 19:15:56 but the same tests also run on AZP, so it's not really needed 19:16:31 ah ok 19:17:33 nitzmahone: do you want to write something about py3.8 and that PR for the bullhorn? Add something to https://github.com/ansible/community/issues/546 19:17:46 will do 19:17:50 cool, anything else to talk about. If not I'll end this as a short meeting and we can go back to our lives 19:18:46 https://github.com/ansible-collections/overview/issues/124 shows what's still using Shippable. 19:19:09 I've got to fix the AWS integration tests 19:21:23 thanks for the info 19:23:51 cool I'm taking the cricket sounds as nothing more to add, will close in 30 seconds 19:25:17 #endmeeting