19:02:20 <bcoca> #startmeeting ansible core public irc meeting 19:02:20 <zodbot> Meeting started Tue Jan 26 19:02:20 2021 UTC. 19:02:20 <zodbot> This meeting is logged and archived in a public location. 19:02:20 <zodbot> The chair is bcoca. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:02:20 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:02:20 <zodbot> The meeting name has been set to 'ansible_core_public_irc_meeting' 19:02:26 <bcoca> #topic https://github.com/ansible/community/issues/584#issuecomment-758884921 19:02:49 <bcoca> stable changes porting guide sections? 19:03:09 <bcoca> those would end up being a merged hash? 19:03:28 * Shrews quits computers FOR.EV.ER. 19:03:52 <sdoran> I usually last a couple of hours when I do that. 19:04:33 <bcoca> hmm, no response, going to move on then 19:04:36 <bcoca> #topic open floor 19:04:37 <sdoran> I feel like this is more of an FYI. 19:04:58 <sdoran> I made that mistake: editing the porting guide directly rather than using fragments for that. 19:05:10 <sdoran> Mainly because I didn't know we had porting guide fragments. 19:05:21 <bcoca> sdoran: we didnt 19:05:24 <felixfontein> hi! 19:05:38 <bcoca> #endmeetingandtakenap 19:05:42 <sdoran> Not sure if there's something for us to do retroactively other than watch for incoming PRs that change the porting guide directly. 19:06:09 <bcoca> sdoran: not even, this only applies to minor releases off stable 19:06:19 <felixfontein> didn't we already talk about this some time ago? 19:06:25 <sdoran> ¯\_(ツ)_/¯ 19:06:30 <bcoca> felixfontein: it was not checked off in ticket 19:06:34 <Shrews> i thought a few meetings ago we agreed to "keep an eye out" for such things 19:06:37 <felixfontein> I remember explaining that in this meeting some time ago :) 19:06:41 <shertel> yeah https://meetbot.fedoraproject.org/ansible-meeting/2021-01-14/ansible_core_public_irc_meeting.2021-01-14-15.00.log.html 19:06:52 <felixfontein> thanks shertel! 19:06:58 <sdoran> shertel++ 19:07:01 <bcoca> then moved on, open floor, updating ticket, will add agenda item to yell at meeting runner that didn't cross it off 19:07:03 <felixfontein> I've now checked it off ;) 19:07:19 <felixfontein> I guess it doesn't hurt to be reminded of it ;) 19:07:35 <bcoca> reminded of what? 19:08:02 <felixfontein> that porting guide changes after the major release should also have changelog fragments with porting guide sections 19:08:33 <bcoca> was being facetious 19:08:57 <bcoca> and you cannot remind me of that which i did not know! 19:09:18 <bcoca> cause i forgot ... 19:09:33 <bcoca> k, if no new items, i'll close in 5 mins before i get into trouble 19:09:50 <felixfontein> :) 19:09:54 <felixfontein> ah, btw 19:10:10 <felixfontein> bcoca: I did split up the PR into two: https://github.com/ansible/ansible/pull/73239 https://github.com/ansible/ansible/pull/73240 19:10:17 <bcoca> i know, on my list 19:10:30 <felixfontein> onw that you have 4 mins... ;) 19:10:53 <felixfontein> (though I guess you're multitasking other things...) 19:11:38 <felixfontein> another potential topic: can https://github.com/ansible/ansible/pull/62027 be backported to stable-2.10 and stable-2.9, as a bugfix? 19:12:09 <Shrews> i still need to review that one for sam 19:12:11 <bcoca> +1 from me 19:12:20 <bcoca> but yeah, once finalized 19:12:24 <felixfontein> Shrews: yes, first it needs to get finalized :) 19:12:28 <sdoran> Oof, that PR. 19:12:30 <bcoca> i would even go back to 2.8 ... but lthat is eol 19:12:35 <sdoran> Makes me want a time machine. 19:12:54 <felixfontein> backporting is the closest approximation to a time machine we have :) 19:13:02 <bcoca> no, that would prevent the 100x 'i told you so' from happening 19:13:16 <bcoca> ;-p 19:13:18 <sdoran> Well, I learned to listen better. :) 19:13:28 <sdoran> Prolonger pain is a good teacher. 19:13:58 <bcoca> k, ending this and giving everyone back their time for getting stuff done 19:14:01 <bcoca> #endmeeting