16:02:33 #startmeeting network 16:02:33 Meeting started Wed Mar 14 16:02:33 2018 UTC. The chair is Qalthos. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:33 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:02:33 The meeting name has been set to 'network' 16:03:15 #chair funzo ganeshrn gundalow privateip rcarrillocruz trishnag 16:03:15 Current chairs: Qalthos funzo ganeshrn gundalow privateip rcarrillocruz trishnag 16:03:53 #link Agenda: https://github.com/ansible/community/issues/247 16:04:00 o/ 16:04:26 #topic Information 16:04:40 2.5.0 is almost out 16:05:10 rc2 is available via `pip install ansible==2.5.0rc2` 16:06:12 Not much on the agenda today 16:06:20 #topic Open Floor 16:06:51 I have one question to ask, May I ? 16:06:59 Anil_, sure 16:07:31 When its likely to have our 2.5 GA, any tentative date ? 16:07:54 @Anil_ probably a few more weeks 16:08:20 Oh.! how many PRs are still pending ? 16:08:56 Anil_ if you have a specific one, please share it. The release is pretty locked down now for testing. 16:10:52 ok.. thats fine. My Manager is curious and keep on asking me these. So just asked it here. No issues 16:11:15 Anil_ sure thing, you know how open source releases go! :-) 16:11:59 Anybody have anything else? 16:13:11 Will there be a specific cadence for dot releases in 2.5? The reason I ask is that we have some upcoming fixes that *might* need to be added to future 2.5 dot releases. 16:13:13 @Qalthos: I just wanted to ask about the procedure of bug fixes 16:14:08 bug fixed now, in which version will they be included? 16:17:12 samerd: when it gets to devel, it will be in the next release. If it gets determined to get picked into an existing release branch, then it goes out with the next point release 16:17:41 so your bug is marked as needing to get picked for 2.5.1, which is when it will likely show up 16:18:18 Qalthos: Thanks for the explanation 16:18:47 mikewiebe: I'm not entirely sure, the release schedule is not a thing I've been paying enough attention to, apparently 16:19:13 if no one else here can answer that, #ansible-devel should know 16:19:58 Qalthos: Thanks, no worries. I will ask on #ansible-devel 16:20:47 Anyone else have anything to discuss? 16:29:18 Right, then 16:29:31 going once 16:29:38 going twice... 16:29:46 thanks Qalthos 16:30:02 And thanks to everyone who showed up 16:30:23 #endmeeting