13:59:50 #startmeeting Fedora IoT Working Group Meeting 13:59:50 Meeting started Wed Apr 24 13:59:50 2019 UTC. 13:59:50 This meeting is logged and archived in a public location. 13:59:50 The chair is pbrobinson. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:50 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:59:50 The meeting name has been set to 'fedora_iot_working_group_meeting' 13:59:51 #chair pwhalen pbrobinson bcotton 13:59:51 Current chairs: bcotton pbrobinson pwhalen 13:59:51 #topic roll call 13:59:56 who is here? 14:00:00 .hello2 14:00:01 bcotton: bcotton 'Ben Cotton' 14:00:07 * pwhalen is here 14:00:23 good morning folks 14:01:14 hello bcotton how are you doing? 14:01:27 pbrobinson: well-caffeinated, and you? :-) 14:01:47 * tdawson is here. 14:01:52 caffeine mostly worn off, other than that doing pretty well 14:02:04 * bcotton pours pbrobinson another cup of coffee 14:03:52 #topic 1) ==== Working Group process and admin ==== 14:04:14 I've only one little bit around this 14:05:01 having spoken with mattdm the thought is it to do full Edition launch a little time after F-30, probably late June with a 30.x minor release 14:05:22 anyone have any thoughts/suggestions around there? 14:05:29 that even, not there 14:05:45 sounds good to me 14:06:21 give attention to just iot, rather than lost in the release announcement 14:07:15 yes, and also allows a little more focus from other teams rather than trying to jam everything into a very short period of time 14:07:26 we'll still have the f30 release as per normal 14:09:08 #info IoT Edition to launch post F-30 release 14:09:36 ah, also not sure I mentioned we have a proper kanban 14:09:49 #info official Fedora IoT kanban https://teams.fedoraproject.org/project/fedora-iot/kanban 14:10:57 we will (me especially) be starting to use this a lot more 14:11:05 so login and make sure you have access 14:11:35 I'm particularly looking at you pwhalen tdawson and bcotton ;-) 14:11:37 I likely have some edits to make there 14:11:40 :) 14:11:58 #info login uses standard Fedora FAS account 14:12:00 i'm good 14:12:19 we imported all the bits over from the other one, I need to work out how to remove that one 14:12:46 #topic 2) ==== Fedora 30 ==== 14:13:12 pbrobinson: Cool ... my account it there ... still checking permissions. 14:13:32 tdawson: just ping on the iot channel if you have issues, doesn't need to be now 14:13:40 *nods* 14:13:43 today's compose will be pretty close to the first RC with the 5.0.9-301 and u-boot 14:14:15 I expect a few more tweaks but overall the basics look fine to me 14:14:35 Raspberry Pi and virt seem in reasonable condition 14:14:48 In the arm meeting, we talked about the 5.1.0 kernel ... I forgot to ask, are we expecting that in the final F30 release? 14:15:34 Which spills into this meeting ... do we expect 5.0.9 or 5.1.0 for the F30 iot image? 14:16:02 tdawson, 5.1 is in rawhide for now. we'll likely ship with 5.0.9 14:16:10 OK 14:17:01 tdawson: nope, not for GA, the rule of thumb for any stable release is that it normally heads to the newest stable Fedora release around the .3 time frame 14:17:14 * pwhalen will upgrade devices today to check the latest compose 14:17:21 *nods* 14:17:40 with rc6 out on Sunday, and normally a rc7 -> .0 that would probably give us around 5-6 weeks before a 5.1.3 heads to F-30 14:18:46 anything else for F-30? 14:19:21 . 14:19:24 * pwhalen has nothing else 14:19:31 #info Talking points needed for F30 14:19:38 #link https://fedoraproject.org/wiki/Fedora_30_talking_points#Fedora_IoT 14:19:54 bcotton: thanks for the reminder, I'll get to that in the next couple of days, for Arm too 14:20:07 pbrobinson++ 14:20:08 bcotton: Karma for pbrobinson changed to 11 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:20:17 (preemptive karma. don't make me regret my cookie) 14:20:29 I do have it already open in my browser 14:20:34 heh :) 14:21:15 #topic 3) ==== Fedora 29 release 2 status ==== 14:21:54 the first compose for this was done today, basically just pulled in all the latest updates 14:22:40 I have a few more bits to land here but overall I don't expect to spend a lot of time on it, and it'll likely be the last f29 release 14:23:35 I've tested it on x86 HW and VM and rpi3 HW and it seems fine 14:23:47 that is more just a heads up 14:23:58 sounds good, with f30 out people will likely move over 14:25:19 yes, and f30 will move to the stable branch once we go GA so it should just happen 14:25:43 but that'll happen a little after release 14:25:56 so as we do the rpm-ostree upgrade, it will transition into F30? correct? 14:27:00 that's the plan 14:27:53 I need to work out exact process and I suspect we'll do that with the .1 release post 30.0 GA 14:28:00 so a couple of weeks later 14:28:31 #topic 4) ==== Fedora 31 planning ==== 14:28:43 it's never too early to start this 14:29:12 #info aiming to work out how best to group f31 planning into a kanban epic to track all the bits 14:29:29 or what ever the big overarching its are for kanban 14:30:20 So we see any big ticket items for F31, or more of getting thigns done already on the kanban board? 14:31:18 /So/Do/ 14:31:29 all of the above 14:32:11 *nods* 14:32:55 does anyone have anything they're planning for F-31? 14:33:47 Not that I'm not going to try to get into F30 :) 14:34:14 big one for me is container pipeline but that's a bit dependent on infra 14:35:03 Ya, containers is what I'd like to start workingon when I get more time. 14:36:17 and end to end demos 14:36:30 Yep 14:36:31 any one anything else for f31 planning? 14:37:02 Not from me. 14:37:54 #topic 5) ==== Open Floor ==== 14:38:17 jsmith: finished the mozilla-iot-gateway review. 14:38:20 jsmith: ++ 14:38:29 jsmith++ 14:38:38 jsmith++ 14:38:42 yes, jsmith++ that was quite a task 14:38:52 looks like it based on the bz 14:39:13 The packages have been built and in going to bodhi now. for F31, 30 and 29 14:39:16 just to backtrack, f31 iot will be based on coreos? 14:40:29 jsmith++ 14:40:36 pwhalen: define "based on", we're already based on the same tech in coreos 14:40:44 Gateway 0.8.1 is out ... I'll be getting that done next week, when the 0.7.0 packages are through bodhi 14:40:55 gateway 0.8.1 has logging, which is something I was wanting. 14:41:07 was looking at changes, for one it doesnt look like they will support updates 14:41:13 from previous releases 14:42:26 actually, looks like its not yet decided 14:42:32 pwhalen: is your question "will f31 IoT be a downstream of CoreOS as opposed to the current state where it's a separate thing that is also built on rpm-ostree?" 14:42:57 tdawson: bodhi will be frozen until release, maybe get 0.8.x into rawhide while f30 settles out 14:43:29 sorta, yes. need to look at the changes between two 14:43:39 pbrobinson: good point ... ok, I'll get 0.8.1 into rawhide. 14:51:05 Did we loose people? Or did my cat do something fancy with my IRC client again? 14:52:03 nope 14:52:11 anyone with anything else? 14:52:25 I'm good. 14:52:59 pwhalen: I think we'll be OK, I don't see the layering functionality being dropped from rpm-ostree, although we've not overly focused on it except for some wifi firmware 14:53:07 * pwhalen is busy reading some of the outdated docs 14:53:39 pwhalen: lets discuss further on IoT channel as necessary 14:53:42 ok, what I'm reading is kinda old. 14:53:54 thank you all 14:53:54 #endmeeting