19:01:12 #startmeeting F16 Release Readiness Meeting 19:01:12 Meeting started Thu Nov 3 19:01:12 2011 UTC. The chair is rbergeron. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:01:20 #meetingname F16 Release Readiness Meeting 19:01:20 The meeting name has been set to 'f16_release_readiness_meeting' 19:01:26 #topic Why are we here? 19:01:45 #info This meeting serves as a last-check, cross-coordination checkpoint across all teams to ensure we are ready for the final release. 19:02:02 #info We'll be checking in with each team to make sure their last-minute items are all complete, and ready to go for Tuesday. 19:02:17 #info The F16 release was just declared GOLD and ready to ship on Tues, Nov. 8. 19:02:24 #topic Who's here? 19:02:27 * nirik waves 19:02:32 #info rbergeron here for FPM and marketing 19:02:43 #info nirik here for infrastructure and probably fesco 19:02:54 sure. I can wear as many hats as needed. ;) 19:02:57 #info adamw, tflink here for QA 19:03:04 yn1v: are you here for ambassadors? 19:03:31 rbergeron, noup ... just curiuos 19:03:41 ah. 19:03:41 * noriko is here for L10N :-) 19:03:51 #info noriko is here for l10n 19:04:00 nirik: major fashion faux pas! 19:04:01 do we have anyone from docs, websites, design? 19:04:07 ambassadors? 19:04:20 adamw: I'm a fashion disaster. ;) 19:04:50 * sijis is here.. representing websites 19:04:58 #info sijis is here for websites 19:05:07 Okay, let's get started. 19:05:13 #topic Marketing 19:05:48 So, I think we're about ready. I am going to do some minor tweaks to the release announcement but it's about ready. 19:06:05 if anyone needs anything from marketing, speak now, or forever hold your peace. :) 19:06:21 #topic Websites 19:06:25 sijis: how goes it 19:06:48 it goes well. 19:06:53 everything ready? 19:06:59 we are making updates and things are looking good for GA 19:07:12 * rbergeron nods 19:07:15 do you need anything from anyone? 19:07:27 from my mental list, we need to update iso link and finish one of the slides on hte homepage 19:07:32 and some spins.fp.o work 19:08:01 #info websites need to update iso link, finish one of slides on homepage, spins.fp.o work. 19:08:27 from design, we may need some images for robotics spins 19:08:27 #info may need images from design for robotics spins 19:08:39 i did update the original request last night, so i hope to hear something by EOD 19:08:39 okay 19:09:00 i think that's all from our side. 19:09:04 okay. 19:09:04 anything needed from us? 19:09:12 * rbergeron looks around for hands 19:09:20 thanks, sijis :) 19:09:41 no problem. i apologize for not being around the last couple of meetings 19:09:48 :) 19:10:03 #topic Infrastructure and FESCo and Possibly rel-eng 19:10:07 Nirik: HI! 19:10:09 hello. 19:10:22 I think things are looking good from all those groups... 19:10:28 fesco has no blockers that I know of. 19:10:39 Infrastructure is ready to start staging stuff for release. 19:10:57 rel-eng should be ready to start staging stuff as soon as dgilmore is around to do so. 19:11:12 Hooray. 19:11:19 Anyone need anything from kevin? :) 19:11:42 #topic QA 19:11:45 as always, coordination in #fedora-admin welcome. 19:11:54 I hope we need nothing from QA, because they haz tired. 19:11:56 * adamw waves beer vaguely 19:11:59 * rbergeron suggests a round of applause 19:12:03 all is good. 19:12:07 (very loud applause) 19:12:12 * adamw redirects it to dev team 19:12:16 ;) 19:12:16 esp anaconda 19:12:45 +1 19:12:45 we just need to bash livecd-iso-to-disk in f14 and f15 a bit (as discussed in go/no-go) 19:12:50 * rbergeron nods 19:12:51 and also fix f14's preupgrade like we did f15's 19:13:03 but aside from that, we're fine. we'll do our usual commonbugs gardening this week. 19:13:14 #info need to bash livecd-iso-to-disk in F14/F15, fix F14's preupgrade as we did F15's. 19:13:22 #info commonbugs gardening ongoing. 19:14:32 Anything else from QA? 19:14:40 or for? 19:14:40 :) 19:14:48 nope! 19:14:50 #topic Design 19:14:54 Do we have anyone repping for design team? 19:15:54 no? 19:16:01 can someone go wrangle someone from there? :) 19:16:06 #topic Ambassadors 19:16:27 yn1v: are things looking okay for ambassadors? 19:16:36 * rbergeron thinks things are all in a row, next step is getting media ordered 19:16:51 I have heard nothing against 19:17:05 we were discussing media ordering for latam 19:17:15 * rbergeron nods 19:17:21 okay. 19:17:26 If anybody needs something from ambassadors i will do my best to push people 19:17:35 okay. 19:18:35 #topic Docs 19:18:38 by the way I saw some event poster, those are very nice :) 19:18:39 jsmith: can you pipe up for docs 19:18:53 * rbergeron waves at digimer 19:18:57 o/ 19:18:59 ;) 19:19:00 rbergeron: I can talk, but I can't give a definitive answer 19:19:13 oh, worth noting, we did get the 16.1 version of the release notes in rc5 19:19:16 * digimer has nothing to add, just wanted to stop by and watch the proceedings 19:19:17 jsmith: if you have suspicions or concerns, I can go figure them out 19:19:17 I think the updated release notes got pushed -- not sure whether they made it into rc5 19:19:23 yes, they did 19:19:26 #info 16.1 version of the release notes went into rc5 19:19:27 That was the only concern I was aware of 19:19:32 cool 19:19:37 missed 'em for rc4 but sneaked 'em into rc5 19:19:45 I think Docs did a great job of staying on top of the ball this release :-) 19:20:08 #topic l10n 19:20:13 noriko: any concerns? 19:20:43 For docs, 10 langauges hits 100% of release notes translation! 19:20:51 awesome work 19:20:57 yeah! 19:21:02 ;) 19:21:06 In total, 19:21:08 That's awesome :-) 19:21:20 #info For docs, 10 langauges hits 100% of release notes translation! 19:21:20 there are 33 languages hit over 80% over all. 19:21:24 https://fedora.transifex.net/projects/p/fedora/r/fedora-main/ 19:21:34 #info 33 languages hit over 80% overall. 19:21:41 kick-ass work, guys :) 19:21:48 yp. 19:21:59 There two things I need your attention. 19:22:08 * rbergeron nods 19:22:16 There is one problem experiencing since F15 and we would like to stop it, and we need developers attention on this. And for next release there is one request regarding the meeting, I need all attendees of this meeting help. 19:22:24 Problem: We are experiencing more streeing freeze break for software. Some reported, thank you. But many of them are not reported, and possibly even not included in F16 release. If effort paid is not included, translator feel demoralized. 19:22:39 streeint/s/string 19:22:55 * rbergeron nods 19:23:16 Is any way to get a little more attention from developers? 19:23:29 Do we think the string freeze timing is just *bad* as it is for developers now, or is it just that they're not paying attention? 19:23:46 I think it's certainly somehting we can address at least with FESCo, and yell a bit more loudly about. 19:23:49 in theory, i guess, string changes are easily detectable with an autoqa test 19:24:00 so we could throw it on the autoqa 'it would be cool if...' list 19:24:07 then we could actually enforce a string freeze... 19:24:42 I think we have a long way to go before that could happen but I'm not against the idea 19:24:44 * rbergeron nods 19:24:51 yeah, note 'theory' =) 19:25:10 #idea Post-release/retrospective note: Need to give more attention to string freeze in the next cycle. 19:25:20 it's essentially just like rpmdiff though i think? since translatable text files should be identifiable in the manifest 19:25:36 adamw: and I'm not as sure it would be easy 19:25:46 welp, file under 'for investigation' 19:26:20 thanks guys 19:27:00 :) 19:27:04 #topic Anyone else? 19:27:13 rbergeron, one 19:27:36 I have one 19:27:41 can someone pull the trigger on my *-announce list mails (/me is getting pulled to run a session at a conference she's at, or somtehing) 19:27:47 noriko: go for itr 19:27:47 rbergeron: I'll do it 19:27:56 Request: Meeting time. I like to request the meeting time to be changed to 20:00UTC from 19:00. Time is too early for me, and asked someone from L10N to replace a couple fo time in the past. No one raise their hand to take the place, so that there might be NO one from L10N will attend for next release if the time stays same. 19:28:30 one hour later shouldn't make much difference to qa team availability, fwiw. 19:28:59 * rbergeron thinks she's okay with that. 19:29:02 WORKSFORME 19:29:06 * noriko bows to adamw 19:29:26 what timezone would that be troublesome for? 19:29:28 europe i guess? 19:29:30 europe, yeah 19:29:42 i guess it's like 9-10pm in russia now 19:30:09 11:30pm 19:30:18 in moscow 19:30:21 prague is 8:30pm 19:30:22 it's 8:30 PM in western europe...I doubt +1h is an issue here 19:30:43 yeah, not really 19:31:05 http://www.timeanddate.com/worldclock/fixedtime.html?iso=20111104T19 19:31:57 okay, I think we're in agreement 19:32:11 #agreed push future release readiness meetings forward one hour 19:32:20 ack 19:32:28 thank you everyone 19:32:45 okay, anyone else? 19:32:48 * rbergeron sets the fuse 19:33:17 #endmeeting