17:36:19 <HelenBailey[m]> #startmeeting Ansible AWS Community Meeting
17:36:19 <zodbot> Meeting started Thu Jul 27 17:36:19 2023 UTC.
17:36:19 <zodbot> This meeting is logged and archived in a public location.
17:36:19 <zodbot> The chair is HelenBailey[m]. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
17:36:19 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:36:19 <zodbot> The meeting name has been set to 'ansible_aws_community_meeting'
17:36:52 <HelenBailey[m]> #chair jillr mgraves
17:36:52 <zodbot> Current chairs: HelenBailey[m] jillr mgraves
17:37:40 <HelenBailey[m]> #topic Mass application of isort prior to stable-7 branching
17:37:54 <HelenBailey[m]> is the question whether we want to do this?
17:38:21 <mgraves[m]> I'm not sure, but if it is then my answer would be yes
17:38:31 <HelenBailey[m]> same
17:38:55 <jillr> agreed
17:40:24 <HelenBailey[m]> #agreed we will mass apply isort prior to stable-7 branching
17:40:54 <HelenBailey[m]> do we want issues/tickets for that?
17:41:21 <jillr> seems reasonable
17:41:39 <tremble> That is what the point was about.  Sorry I'm late
17:41:49 <HelenBailey[m]> tremble: No worries!
17:42:40 <tremble> I'd say yes create an issue and add it to the 7.0.0 target
17:43:24 <tremble> S/target/milestone/
17:43:31 <HelenBailey[m]> for amazon.aws and community.aws?
17:43:34 <tremble> Yes
17:43:44 <HelenBailey[m]> I can do that
17:44:09 <HelenBailey[m]> anything else on isort?
17:44:24 <tremble> Nah, it's pretty simple
17:44:53 <HelenBailey[m]> great, next topic is Github releases
17:45:54 <HelenBailey[m]> I noticed (and someone else mentioned here recently) that the releases on Github don't match the releases on Galaxy/Automation Hub. Is there a reason for that?
17:46:12 <HelenBailey[m]> It looks like we have historically not created Github releases very consistently, maybe?
17:46:21 <tremble> We keep forgetting to "release" in GitHub
17:46:30 <jillr> we have historically not done releases on Github, yeah
17:46:51 <HelenBailey[m]> well, there are some. for example https://github.com/ansible-collections/amazon.aws/releases
17:46:52 <jillr> if we want to start doing that, consistently, it needs to be built into the release pipeline
17:47:31 <tremble> We tag releases, so we can also retrospectively add the releases
17:47:54 <tremble> s/releases/when we actually release/
17:48:29 <HelenBailey[m]> do we want to add all of them?
17:48:43 <jillr> we can totally backfill.  but we shouldn't depend on manually adding future releases if we want releases to be on GH
17:49:19 <tremble> Yeah, +1 to jillrs comment
17:51:06 <jillr> pondering this... if we add it to the current pipeline it will affect almost all collections.
17:51:35 <jillr> It should be automated, but would it make sense to be an additional pipeline or workflow collections can opt-in to?
17:52:10 <tremble> We could do it as an action triggered by tagging...
17:53:17 <HelenBailey[m]> yeah a new Github Actions workflow seems like the best option
17:53:31 <HelenBailey[m]> that way we can apply it only to the repos we want
17:54:46 <jillr> +1
17:55:56 <tremble> I can't guarantee timelines, but I can probably have a play before the Sept releases
17:56:44 <jillr> thx tremble
17:57:04 <HelenBailey[m]> should this be in the https://github.com/ansible-network/github_actions repo as a shared workflow?
17:57:41 <tremble> Eventually
17:59:03 <HelenBailey[m]> does anyone want to volunteer to backfill prior releases?
18:00:00 <HelenBailey[m]> resounding silence :)
18:00:11 <HelenBailey[m]> I can do it but do we need to go all the way back to the beginning?
18:00:37 <jillr> we can put it in the team backlog, as long as the ticket has a process to follow, and try to prioritize it so it doesn't get lost
18:01:02 <mgraves[m]> is there value in having old releases in github?
18:01:05 <jillr> in theory it's not a large task, it just needs to get done
18:01:19 <jillr> mgraves[m]: aiui users have gotten confused when they aren't there
18:01:54 <HelenBailey[m]> yeah I think it's just confusing for it to be inconsistent across platforms
18:02:10 <tremble> I've had confused colleagues, they looked at GH rather than Galaxy
18:02:43 <mgraves[m]> I'm on board with releases going forward, was just wondering if there's value in creating releases for historical tags
18:02:48 <flowerysong> I think the important thing is for there not to be gaps, but that doesn't mean backfilling all the way to the beginning.
18:03:35 <jillr> maybe we just pick a historical point in time to go back to?  stable-4 or stable-5?
18:03:52 <mgraves[m]> I like stable-5
18:04:09 <jillr> in theory it could be scripted with the GH api to reduce the toil of going backwards
18:04:16 <tremble> See what the first currently added release is?
18:05:00 <mgraves[m]> +1
18:05:30 <HelenBailey[m]> amazon.aws 5.0.0
18:05:45 <jillr> stable-5 it is then
18:06:19 <HelenBailey[m]> great! anything else on Github releases?
18:07:34 <HelenBailey[m]> if not we can move on to the last agenda item
18:07:40 <HelenBailey[m]> We agreed to release on a monthly basis on the first Tuesday of the month. We should ensure we're on track for the following releases:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/bd2e162fde409e165cf999988daad3c55c9bbb87>)
18:11:08 <mgraves[m]> are there any PRs we want to get merged before we do releases?
18:13:37 <HelenBailey[m]> on amazon.aws, I think a few of the bugfix PRs are ready or almost ready to merge
18:15:27 <mgraves[m]> can we attach 5.x/6.3 milestones to what we want to prioritize?
18:16:49 <tremble> Mgraves: That's what they're there for :)
18:18:06 <HelenBailey[m]> yeah. I can do that for 1664, 1657. I'm not sure about the new features (1631, 1647)?
18:19:02 <HelenBailey[m]> and I'm not sure about any of the open prs in community.aws
18:33:04 <HelenBailey[m]> ok done. I think 1631 is ready to merge so added it to 6.3.0. I'm not sure 1647 will be done in time
18:35:58 <HelenBailey[m]> for community.aws I assume we want to merge 1875
18:38:33 <HelenBailey[m]> anything else we want to make sure gets into the next release?
18:40:44 <HelenBailey[m]> if any other prs or issues seem important and achievable by Tuesday, go ahead and add them to the milestones
18:41:03 <HelenBailey[m]> that's everything that was on the agenda. anything else we need to discuss today?
18:42:05 <jillr> nothing here
18:44:18 <HelenBailey[m]> ok, thanks all!
18:44:32 <HelenBailey[m]> #endmeeting