00:01:48 #startmeeting F-13-Beta engineering readiness meeting 00:01:49 Meeting started Thu Apr 8 00:01:48 2010 UTC. The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:01:51 Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:01:53 #meetingname f-13-beta-eng-readiness 00:01:55 The meeting name has been set to 'f-13-beta-eng-readiness' 00:01:59 #topic Waiting for critical mass 00:02:22 we have folks from QA, RelEng and Development around? 00:02:43 * nirik is around. 00:02:54 nirik: howdy 00:03:07 Hopefully this will be a short and happy meeting. ;) 00:03:25 agreed ... let's wait a few more minutes for the other usual suspects 00:03:51 * stickster lurks 00:04:13 lurker! 00:04:27 a meeting at this time? 00:04:36 adamw: Oxf13 around? 00:04:51 hiya 00:04:56 it's a stealth meeting 00:05:02 um... 00:05:03 heh 00:05:10 shouldn't this come after the go / nogo meeting? 00:05:37 engineering readiness? 00:05:43 * Oxf13 thinks something didn't get correctly shifted with the slip 00:06:16 maybe I'm confused. 00:06:27 we've got it on the calendar for now ... 1 week after last weeks slip decision 00:06:39 should be quick ... let's get moving 00:06:41 oh, engineering readiness == go / no go? 00:06:54 Oxf13: yeah, you got it 00:07:17 alright ... standard intro for those not familiar with the purpose of this meeting ... 00:07:20 #topic Why are we here? 00:07:25 #info The purpose is to decide whether the beta has met the release criteria 00:07:30 #link https://fedoraproject.org/wiki/Fedora_13_Beta_Release_Criteria 00:07:46 We've got adamw representing QA, Oxf13 representing RelEng 00:07:47 * adamw still doesn't quite understand why this meeting has two names 00:08:00 adamw: we can figure that out later :) 00:08:11 I don't either. I've only ever heard of it called the go / no go meeting 00:08:37 I've not changed the meeting name since last week 00:09:01 but can easily make changes for the next meeting 00:09:07 just not now 00:09:14 yeah, just a side note. 00:09:18 * Oxf13 doesn't care either way 00:09:39 nirik: care to represent development today? 00:09:49 uh, sure. ;) 00:10:11 :) ... typically I bug notting, but he's not around during this time 00:10:15 nirik: thx 00:10:27 alright ... the meat of this meeting ... 00:10:30 #topic Go or No Go? 00:10:44 adamw: how we holding up with the beta release criteria? 00:11:25 looking pretty good 00:11:31 we have a few caveats on the install matrix 00:12:03 if you look at https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test , there's some beta level tests with 'fails', but individually, the bugs don't count as blockers 00:12:16 we mostly established all of them in rc3 testing, anyway, there's nothing new there 00:13:54 we have one bug left on the blocker tracker 00:14:08 that's https://bugzilla.redhat.com/show_bug.cgi?id=579739 00:14:26 but jlaska and i feel it should be dropped; it was a transient update fail which went away after a reboot, and others haven't seen it 00:14:56 others have done updates on newly-installed beta rc5 and succeeded, i've been using gpk for updates for a month or so and haven't had any unavoidable failures with the latest version 00:15:04 anyone else here had real troubles with updating? 00:15:39 * nirik has been using yum. ;( 00:15:42 for those wanting the take-home version of this test - https://fedoraproject.org/wiki/QA:Testcase_desktop_updates 00:16:31 * stickster has been using gpk fairly regularly too 00:16:38 * poelcat here 00:16:45 adamw: I've been using gpk and yum ... haven't seen this issue. But given the interaction quirks we've seen throughout F-13 with gpk, we both indicated we wouldn't be surprised if additional issues lurked 00:17:13 sure, i wouldn't either. but bottom line we're not aware of unavoidable breakage. there are occasional weirdnesses, but they tend to go away if you quit and try again. 00:17:52 I think the take away here is that it doesn't fail every time for everybody, which OK for me 00:18:35 heh 00:18:46 well, the most important is that it doesn't fail every time for _anyone_, as far as we know. 00:19:00 so, yeah, executive summary, QA is feeling good about RC5. 00:19:32 alright, I'm hearing a _GO_ from QA 00:19:40 adamw: thanks for the updates 00:19:59 Oxf13: nirik: anything on your radar that would impact the beta release criteria? 00:20:08 nothing I can think of off hand. 00:20:21 nothing here. 00:20:33 alright ... time for #agreed 00:20:51 #agreed The Beta release criteria have been met with F-13-Beta-RC5 00:21:00 insert thunderous applause here 00:21:08 * nirik cheers 00:21:17 \o/ 00:21:20 rockin. 00:21:39 tomorrow's branched compose will include the kernel and plymouth we pulled in, and will be the "go here for source" link for the live images 00:21:43 will drop the update bug from the blocker list 00:21:47 then we'll get updates flowing again. 00:21:55 #topic What's next? 00:22:22 #info adamw removing bug#579739 from F13Beta 00:22:50 Oxf13: anything on your radar for mirrors? 00:22:59 staging to start tomorrow likely 00:23:06 okay ... 00:23:32 #info RelEng will begin staging to mirrors starting Thu Apr 8 00:23:53 anything else we need to discuss here, that won't be covered in the release readiness mtg tomorrow? 00:24:06 Oxf13: let me know if you want torrent preseeding. 00:24:53 will do 00:26:02 * nirik has nothing else off hand. 00:26:16 do we typically announce _GOLD_ after this meeting? 00:26:23 sortof? 00:26:26 it's not official 00:27:01 okay, then I think we're good here 00:27:04 jlaska: You mean announce the Beta, or just that we have a Beta forthcoming? 00:27:19 stickster: just that it's all systems go 00:27:41 or is the meeting recap sufficient? 00:27:56 I'll announce tomorrow what's going on with beta and what maintainers can expect out of the Branched repo in the next few days 00:28:02 meeting recap is sufficient 00:28:08 perfect 00:28:17 Right on. Usually no announcement until there's something official to download. 00:28:24 alright gang ... I'll #endmeeting in 1 minute 00:29:04 ... 20 seconds 00:29:29 thanks folks ... nice work all around with the Beta! 00:29:32 #endmeeting