18:09:42 <jwb> #startmeeting
18:09:42 <zodbot> Meeting started Fri Aug 23 18:09:42 2013 UTC.  The chair is jwb. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:09:42 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:09:47 <jwb> yay
18:09:54 <jwb> #meetingtopic Fedora Kernel
18:10:07 <jwb> #meetingname Fedora Kernel
18:10:07 <zodbot> The meeting name has been set to 'fedora_kernel'
18:10:12 <jwb> #topic init
18:10:15 <jwb> who all is here
18:10:22 * nirik is lurking around.
18:10:29 <jforbes> it appears zodbot is here this time
18:11:34 <jwb> i'm guessing davej will show up at some opint
18:11:45 <jwb> let's get rolling.  release overview first
18:11:51 <jforbes> at some pint?
18:11:57 <jwb> #topic F18
18:12:03 <jwb> jforbes, possibly!
18:12:24 <jwb> jforbes, wanna tell us about the awesomeness that is f18?  probably f19 at the same time
18:12:26 <jforbes> So, F18 and F19 can really be put into one topic at this point
18:12:29 <jforbes> hah
18:12:31 <jwb> #topic F18/F19
18:12:50 <jforbes> Right now, both are on 3.10.9
18:13:34 <jwb> #info Currently on 3.10.9
18:13:38 <jforbes> We have a new issue now in pushing updates (which is better than the old issue). The last couple of updates I have pushed have received stable karma before they even got into updates-testing
18:14:36 <jforbes> While this is much better than never getting enough karma for the older release, this is also suboptimal.  I think the solution at this point is to turn off auto karma for the initial push.  Wait until it gets to updates-testing for a day, then turn on auto karma to let it push out to stable
18:15:28 <jwb> yeah
18:15:32 <jforbes> So basically people should still be testing and giving karma as always, but we give it a day with the broader audience to make sure there is nothing big that impacts a large number of users who just don't bother to follow bodhi
18:16:22 <jwb> #info Updates to be filed with auto-karma off to ensure at least one day in updates-testing
18:16:42 <jwb> #info Lots of testers have shown up all of a sudden.  Yay badges?
18:16:54 <jforbes> As a side note, I really do appreaciate those who are actively testing and giving karma.  I hope the trend continues
18:16:55 <nirik> could be. ;)
18:17:35 <jwb> jforbes, definitely
18:18:02 <jforbes> I think that is all of note for 18/19
18:19:29 <jwb> the biggest issue i know of there is the S/R problem on a variety of thinkpads
18:19:35 <jwb> 400 and 500 class
18:19:49 <jwb> i think we've established that the mei mei_me drivers are crap here
18:19:57 <jwb> blacklisting them "fixes" things at least
18:20:13 <jforbes> Right, there was talk at flock abotu disabling them all together
18:20:16 <jwb> so right now i have a scratch build going with all the currently queued mei patches for people to test
18:20:36 <jwb> if that fails, then yeah we might disable
18:21:16 <jforbes> But I don't know that it's the best option either. Fedora may not have a lot of people actively using the functionality, but I am sure there are some, and shaking out the bugs is the better thing to do
18:21:45 <jwb> yeah... but i guess i'd rather point them at f20/rawhide to do the shaking instead of breaking people that don't care on stable releases
18:21:54 <jforbes> Very true
18:22:02 <jwb> to be determined i guess.  i hope the scratch build works
18:22:20 <jwb> ok, moving on
18:22:27 <jwb> #topic F20/Rawhide
18:22:45 <jwb> #info F20 and Rawhide are kept in sync for now.  both at 3.11-rc6-gitX
18:23:00 <jwb> things are mostly smooth there, but that's likely lack of testers too
18:23:17 <nirik> working ok here, aside a gpu hang this morning.
18:23:35 <jwb> at the moment, F20 looks to be released with 3.11.y kernels.  unless we slip again, just not enough time to squeeze in 3.12
18:23:43 <jwb> anyone disagree at this piont?
18:23:52 <jwb> why can i not type p o i n t today
18:23:58 <davej> unless there's mad slippage, yeah
18:24:14 <jforbes> I think it would have to be major slip considering a rebase before release
18:24:42 <jwb> hopefully the rebase will be in decent shape, since 3.12 should start up within the next few weeks
18:24:52 <jwb> but... requires testers ;)
18:25:05 <jwb> #info F20 to be released with 3.11.y
18:25:21 <jwb> anything else on these?
18:25:56 <jwb> ok.  wanted to briefly highlight some of the stuff we're going to focus on next month
18:26:03 <jwb> #topic next month
18:26:50 <jwb> jforbes and i are going to be at LPC at the end of the month.  we'll be doing secure boot stuff and i plan on attending the coreOS talks too
18:27:01 <jwb> mostly mingling, hallway track, etc
18:27:25 <jwb> in addition to that, jforbes is going to start packaging up the kernel-tests we have to make them easier to install and run
18:27:34 <jwb> reviewers welcome :)
18:27:43 <davej> huh, still no schedule published for lpc
18:27:43 <jforbes> Also, the kernel test suite will be packaged next month, possibly with badge integration (optional)
18:28:05 <jwb> davej, the referred tracks are avaiable.  uconfs aren't yet other than "these are the one's we're doign"
18:28:32 <jwb> er, referreed
18:29:02 <jwb> davej will be doing more trinity work as well as coverity scans
18:29:10 <jwb> and holding down the fort while jforbes and i are gone
18:29:52 <jwb> the intention here is to start focusing on upstream testing, bug finding, and bug fixing
18:30:07 <jwb> so hopefully those bugs don't ever make it to our users, with the exception of people running rawhide
18:30:11 * jwb waves at nirik
18:30:21 <nirik> :)
18:30:51 <jwb> i'll be poking at secure boot stuff and diving into f20 release/blocker meetings as needed
18:31:01 <jwb> and then doing bug triage stuff
18:31:22 <jwb> anything i missed or any questions?
18:32:26 <jwb> #info Justin and Josh at LPC
18:32:37 <jwb> #info kernel test suite being packaged up
18:32:53 <jwb> #info trinity and coverity scans
18:33:11 <jwb> ok, we'll open floor it for a minute or two
18:33:16 <jwb> #topic open floor
18:33:29 <jwb> <crickets>
18:34:41 * nirik has nothing really.
18:34:59 <jwb> nirik, threebean: if we wanted kernel specific badges, just open a ticket in trac requesting them and describing how to earn them?
18:35:12 <nirik> yep. There's a process/guide on the trac instance.
18:35:21 * threebean nods
18:35:24 <threebean> yes, please :)
18:35:25 <jwb> ok, cool
18:35:31 <nirik> they could be for something we can award based on fedmsg messages, or one-offs for one time things...
18:35:45 <jwb> yeah, i have a few ideas
18:35:53 <jforbes> threebean: more importantly, I need to get with you next week to see how we can push test messages to the bus.
18:36:13 <threebean> jforbes: sounds great.
18:36:34 <threebean> there's been more of that kind of thing since badges went live.  someone from qa is working on getting their stuff on the bus too.
18:36:44 <jwb> nice to see
18:37:10 <jwb> ok, let's close it out for the week.  thanks for coming everyone
18:37:18 <jwb> #endmeeting