17:34:46 #startmeeting Ansible AWS Community Meeting 17:34:46 Meeting started Thu Jun 22 17:34:46 2023 UTC. 17:34:46 This meeting is logged and archived in a public location. 17:34:46 The chair is abuzachis[m]. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 17:34:46 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:34:46 The meeting name has been set to 'ansible_aws_community_meeting' 17:35:20 #chair tremble Helen Bailey 17:35:20 Current chairs: Bailey Helen abuzachis[m] tremble 17:36:03 #topic AWS collection releases 17:36:21 I added an item to the agenda https://github.com/ansible/community/issues/687 17:37:10 #info The next release cycle should happen on July 4th. Are we on track for the upcoming releases? 17:38:34 For the amazon.aws collection we have these PRs https://github.com/ansible-collections/amazon.aws/pulls right now 17:39:08 I got a couple of PRs I'd like to get into 6.x. 17:39:42 Awesome! Would you mind creating a milestone and add those to the milestone? 17:40:14 - 17:40:15 Instance Profiles - https://github.com/ansible-collections/amazon.aws/pull/1614 17:40:15 ARN helpers - https://github.com/ansible-collections/amazon.aws/pull/1619 17:40:15 GovCloud ARN fixes - https://github.com/ansible-collections/community.aws/pull/1848 (needs 1619 which is why there are sanity failures) 17:40:36 Sure. Do you know how? 17:41:56 I'm creating the milestone if you want, it will be 6.2.0 I assume 17:42:20 Yeah c.aws 6.1.0 and a.aws 6.2.0 17:42:46 https://github.com/ansible-collections/amazon.aws/milestones 17:43:58 We already have the 6.1.0 milestone in c.aws. I updated the due date only to match July 4th https://github.com/ansible-collections/community.aws/milestones 17:44:53 Also, there's public holiday in US on July 4th. Do we want to postpone to July5th for this time? 17:46:11 Or keep July 4th and however we know that we will be releasing on July 5th, just to give time to folks in US to review or merge something. As you prefer! 17:47:07 If it's being run by folks in the EU I wouldn't worry about it. (Where's Helen based out of?) 17:47:28 Boston :) 17:48:04 amazon.aws I'd say that's a call for the cloud team, if you'd rather US folks approve we can either prep it early, or push it. 17:48:14 * push it out later. 17:48:39 yeah the cloud team agreed if there are enough non-US folks available (and for this holiday there are) we could go ahead on the planned date 17:49:21 I should be able to review, but I don't know what my schedule's going to look like for the next 3 weeks or so. "life" 17:50:12 I would say to keep July 4th and if there won't be people to review on that date, wait until July 5th. 17:50:58 just curious, what's our practice around adding things to GH milestones? issues we want to see fixed? PRs in flight? presumably no need to add already merged PRs 17:52:06 It's kinda fluid. Mostly they're added ad-hoc if they're on someone's priority list or if it comes up here. 17:55:37 Sometimes issues get put into them too 17:56:55 I just added an issue I filed (and plan to PR a fix for next week) 17:57:12 mostly as a reminder to get it done by then :) 17:59:35 Coming to this is what we have unmerged c.aws https://github.com/ansible-collections/community.aws/pulls 18:01:20 Finally, we have merged this PR https://github.com/ansible-collections/community.aws/pull/1799 and disabled the corresponding tests on zuul. I hope we could see an improvement in the CI. 18:01:35 The SSM pieces I've just not had the motivation to try and figure out what's going on with that plugin again, I suspect some of the recent bash defaults changes are breaking things 18:03:24 I'm unlikely to get to them before August because $life 18:03:50 No worries! 18:05:13 Do you have anything else to add on this topic? 18:05:36 nope 18:06:49 Or something else you would like to discuss? 18:07:15 nothing for here :) 18:08:47 nothing from me 18:09:22 Ok, I will end the meeting then. I f something else pops up we can always discuss after. 18:09:23 #endmeeting