19:01:35 #startmeeting F22 Beta Readiness Meeting 19:01:35 #meetingname f22-beta-readiness-meeting 19:01:35 Meeting started Thu Apr 9 19:01:35 2015 UTC. The chair is jreznik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:35 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:01:35 The meeting name has been set to 'f22-beta-readiness-meeting' 19:01:41 .hello adamwill 19:01:42 adamw: adamwill 'Adam Williamson' 19:01:45 #topic Roll Call 19:01:46 .hello pfrields 19:01:47 stickster: pfrields 'Paul W. Frields' 19:02:04 and hi everyone joining us today! 19:02:21 .hello roshi 19:02:22 roshi: roshi 'Mike Ruckman' 19:02:25 .hellomynameis jzb 19:02:26 jzb: jzb 'Joe Brockmeier' 19:02:43 fancy meeting you cowpokes here ;-D 19:03:20 .hello kevin 19:03:21 nirik: kevin 'Kevin Fenzi' 19:03:45 .hello immanetize 19:03:47 randomuser: immanetize 'Pete Travis' 19:03:54 .hello juliuxpigface 19:03:57 juliuxpigface: juliuxpigface 'None' 19:04:29 .hello sgallagh 19:04:30 ok, let's begin! 19:04:33 sgallagh: sgallagh 'Stephen Gallagher' 19:04:56 #topic Purpose of this meeting 19:04:58 #info "Before each public release all of the groups participating the development of Fedora's next release meet to make sure the release is well coordinated." 19:04:59 #link https://fedoraproject.org/wiki/Release_Readiness_Meetings 19:05:16 #topic Current status 19:06:00 so I'll start with a sad news but we had to slip due to last minute blocker bug 19:06:20 I'm updating schedules right now and I'll send announcement after this meeting 19:06:34 #link https://fedoraproject.org/wiki/Releases/22/Schedule 19:06:41 Yeah, saw that. I know it's a bit of a heartbreak 19:07:17 we were doing it for robyduck, he asked for one more week for websites :) 19:07:29 yeah, that 19:07:36 haha 19:07:40 .hello oddshocks 19:07:41 oddshocks: oddshocks 'David Gay' 19:07:54 .hello mohamedfawzy 19:07:55 Mohamed_Fawzy: mohamedfawzy 'Mohamed Fawzy' 19:07:59 #topic Ambassadors 19:08:16 ok, do we have anyone for ambassadors section? 19:08:22 .hello fedorauser 19:08:24 FedoraUser: fedorauser 'Medic Momcilo' 19:09:14 for Beta, we're usually good so I can check it out later offline 19:09:22 jreznik: iam fedora ambassador in Egypt 19:09:42 Mohamed_Fawzy: hi, I know - is there anything ambassadors needs for Beta? 19:11:13 * jreznik thinks we can safely move on 19:11:25 #topic Documentation 19:11:33 randomuser: your turn 19:11:47 * randomuser clears throat 19:12:04 I think we're in good shape for Beta (given the slip :P) release notes 19:12:20 a few of us will be working hard at it this week 19:12:37 there are a few points I would like some collaboration on, though 19:12:50 #info documentation is in a good shape for Beta release notes 19:13:14 sure, we all try to help 19:13:19 sgallagh, I'm going to play with the database server role today and it would be nice to have a review of what I come up with, and what we're saying in general. Will probably ping on.. Monday 19:13:28 ack 19:13:48 I had some cloud questions that roshi was able to answer this morning 19:14:07 and I can answer more should they come up 19:14:30 and Workstation... stickster, maybe you can help me figure out what's new there besides the obvious work on gnome 3.16 19:14:52 randomuser: sure, hit me up directly after thsi 19:14:54 *this, even. 19:15:03 great, thanks 19:15:40 this is the way I really like it, anything else randomuser? 19:15:40 in general, those following the DNF replacement saga could provide feedback on what I've written about it 19:15:47 almost done 19:16:22 https://fedoraproject.org/wiki/Documentation_Server_Configuration_Tools_Beat#yum_replaced_by_dnf ( plus a paragraph in git about yum-deprecated) 19:16:23 #info dnf release notes review/feedback requested by documentation team 19:16:34 sorry for interrupting you :) 19:16:42 a lot of concerns about dnf, we want to answer all questions we can 19:16:54 core guides should be updated between beta and final 19:17:11 with maybe some bonus guides to help new users, we'll see 19:17:55 that's all from me; please communicate if you want something documented 19:18:13 #info core guides should be updated between beta and final 19:18:53 #info communicate to documentation if anybody wants something documented 19:19:44 randomuser: is it all from docs? 19:19:50 are we writing anything about the changes to the way products/flavors are implemented? 19:20:04 * stickster wields a bit of editing pen... 19:20:14 adamw, I'm not sure what that means 19:20:19 it would be nice to document it (if it is not) 19:20:21 stickster, in git! 19:20:49 mattdm/sgallagh rejigged the fedora-release-foo and config subpackges and stuff somehow 19:20:50 randomuser: I'm on the wiki now, is that not the right place? 19:21:33 Hopefully that information is only interesting to packagers 19:21:44 stickster, it depends on the page, probably; we're right in the middle of migrating. I linked to the wiki so everyone doesn't have to read raw docbook today, but the dnf stuff for example is committed 19:21:45 There should be little impact to end-users 19:22:00 randomuser: I'm on https://fedoraproject.org/wikiDocumentation_Server_Configuration_Tools_Beat 19:22:16 i'll add a short paragraph; impact or no, it is an integral part of the machine 19:22:16 (or rather, the impact that F21 had should no longer be there) 19:22:39 stickster, ok, I can check that for changes if you prefer to edit there 19:22:49 randomuser: Whichever is easiest for you I can do 19:22:57 git is better, please 19:23:05 randomuser: OK, point me to the repo and I'll do that 19:23:16 * stickster lets folks get on with it here ;-) 19:23:22 ssh://git.fedorahosted.org/git/docs/release-notes.git 19:24:19 #action randomuser to document fedora-release package situation 19:24:23 eof 19:24:33 thanks a lot randomuser! 19:24:42 #topic Fedora Engineering Manager 19:24:50 stickster: anything from you? 19:25:01 nope :-) 19:25:12 ok, moving on 19:25:16 #topic FESCo 19:25:29 nothing in particular from fesco 19:25:29 nirik, sgallagh: anything from fesco for Beta? 19:25:41 There was a blocker for anaconda passwords, but it's landed and in rc1 19:26:06 #info nothing particular from FESCo, FESCo blocker for Anaconda passwords resolved in RC1 19:26:32 There was some ambiguity about release-blocking media 19:26:48 We probably need to clarify a process for controlling that 19:27:07 indeed 19:27:29 sgallagh: good idea yeah. 19:27:40 can anyone file FESCo ticket for it? I can but tomorrow 19:28:08 well, I think basically we need a wiki page with a policy and then note it to everyone. 19:28:18 #info there was some ambiguity about release-blocking media, we should clarify 19:28:18 it was on my list of things to do after the cloud discussion 19:28:33 I'm not sure removing a 'release-blocking' sticker from a given deliverable and shipping it with flaws is a great approach... but, this isnt' the place to dive into that 19:28:56 randomuser: it's not about that really. 19:29:11 randomuser: It's about describing exactly when in the process we decide what is release-blocking. 19:29:16 it's about: "here are the exact things that are release blocking:" "here is how you add to or remove from this list" 19:29:17 randomuser:the plan was to review here what to do in case it's not blocking but broken but as we're slipping 19:29:19 I think that has to happen prior to Alpha Freeze, personally 19:29:27 sgallagh: +1 19:29:29 +1 to that 19:29:30 And what nirik said as well 19:29:33 sgallagh: or better long time ago 19:29:44 it's all kind of just assumed from the past. 19:29:46 ack 19:30:09 nirik: well, we know old stuff, atomic is new... 19:30:21 jreznik: Strictly speaking, all of the Edition stuff is new too 19:30:22 right, but also "atomic" isn't detailed enough. ;) 19:30:30 It just kind of happened last cycle 19:30:58 nirik: we have made explicit decisions before and written them into the criteria, but it's always been a as-it-comes-up sort of thing. 19:31:06 sgallagh: but we somehow sorted it last cycle but makes sense to go through it and maybe it can be part of the process to review for each upcoming release 19:31:16 sure, it would be nice to have a exact list. 19:31:27 is there a documented process for something to become a product/flavor/edition yet? 19:31:28 the current wording is "The term release-blocking images means all the images in which bugs are currently considered capable of blocking a Fedora release. The current set of release-blocking images includes the images defined by the three primary Products - Server, Workstation and Cloud - in their product requirement documents and/or technical specifications, and the KDE live image. " 19:31:44 it would be easy to say "all approved editions are release blocking" 19:32:09 but in that case cloud is a bit wishy washy. 19:32:10 Unfortunately, the Cloud PRD has aged out and may no longer be accurate 19:32:16 That will have to be revised for F23 19:33:08 I'm fine with them defining that, but I think there should be a central list and only action adds to it. 19:33:15 it's out of scope here but let's make sure it's going to happen 19:33:22 yeah, off trac 19:33:27 agreed (both nirik and jreznik) 19:33:28 nirik: I agree 19:33:58 so in the end it makes sense to track it as FESCo ticket? to make sure it happens 19:34:04 yes 19:34:38 sure 19:34:39 if nobody does it by tomorrow, I'll do it... 19:34:54 thanks 19:35:07 not sure I still have mental capacity for all stuff tonight (with schedule updates ;-) 19:35:11 moving on 19:35:24 #topic Marketing 19:35:30 jzb: still around? 19:35:56 yep 19:36:22 we have the beta announcement in a mostly complete state 19:36:32 it'll be ready for the beta 19:36:42 #info the beta announcement in a mostly complete state, it will be ready for the beta 19:36:56 IIRC we also have something around bookmarks, and I'm not entirely sure that's complete 19:37:11 bookmarks? 19:37:38 sgallagh: I think marketing is supposed to review the default FF bookmarks each release 19:37:48 ah 19:37:49 and if I'm not mistaken, beta is the target date for that. 19:37:55 argh 19:37:59 I'm unlear that has happened. 19:38:04 yep, to make sure it's not out of date but I think it's for final 19:38:14 not sure right now, I'll check it up 19:38:15 any other marketing stratagems, jzb ? social media campaigns, targeted ads of some sort, swag, coordination with ambassadors or regional activists? 19:38:55 randomuser: for beta? No. And we don't have a targeted ad budget that I'm aware of ;-) 19:39:07 jzb: http://pkgs.fedoraproject.org/cgit/fedora-bookmarks.git/tree/default-bookmarks.html 19:39:23 heh. That's how it is, until people start asking awkward questions :) 19:39:42 jzb: no super bowl ad ever? 19:39:48 also, as always, I'll mention... help wanted. 19:40:01 * jreznik is trying to help 19:40:04 I checked ff bookmarks for the F21 19:40:11 we have a fair number of folks doing work around the Magazine, but other than that, marketing is a bit thin these days. 19:40:19 mailga: What did you find? 19:40:20 I take care of also for F22. 19:40:21 #info mailga checked ff bookmarks for F21 19:40:25 mailga: do you wish to do f22 19:40:30 jreznik: you do, and it's appreciated. 19:40:31 #undo 19:40:31 Removing item from minutes: INFO by jreznik at 19:40:21 : mailga checked ff bookmarks for F21 19:40:37 oh, sorry, mailga -- I made a mistake f21/f22 :-) 19:40:46 * randomuser is at capacity for volunteer cycles, unfortunately 19:40:47 stickster: me too :) 19:41:00 randomuser: aren't we all? :-) 19:41:23 #action mailga to check F22 FF bookmarks 19:41:46 EOF for me 19:41:51 thanks jzb 19:42:06 mailga: I see one bit wrong already, Join Fedora link should be -> https://fedoraproject.org/wiki/Join (as sad as that is) 19:42:13 #help marking folks are always looking for help. 19:42:13 #topic Infrastructure 19:42:20 nirik: you again :) 19:42:35 we should be all set once we have stuff to distribute. ;) 19:42:44 stickster: thanks 19:42:54 stickster, we have been rumbling about such things in the join sig context, all welcome :) 19:42:58 #info infrastructure should be all set once they have stuff to distribute 19:43:10 #topic QA 19:43:11 randomuser: ack 19:43:16 adamw, roshi: ? 19:43:28 aside from the standing blocker, I have nothing 19:44:17 ok 19:44:36 yeah, nothing much 19:44:39 test coverage looks decent i think 19:44:49 * roshi thought so too 19:45:08 #info outstanding blocker, test coverage looks decent 19:45:19 thanks adamw/roshi 19:45:20 #topic Release Engineering 19:45:36 dgilmore: are you around? anything from you for Beta? 19:45:41 we will be ready when there is a release ready to go 19:45:57 we do need to add the atomic installer for RC2 19:46:08 #info releng will be ready when there is a release ready to go 19:46:20 #info releng do need to add the atomic installer for RC2 19:46:58 thanks dgilmore 19:47:07 #topic Translations 19:47:20 do we have anyone from i18n? 19:47:35 l10n ? 19:48:06 or i10n :) 19:48:24 * jreznik will check offline with noriko 19:48:27 sorry, not trying to be pedantic 19:48:49 randomuser: np, it's always the question what's more accurate in which context 19:49:17 #topic Design 19:49:41 * jreznik pinged mizmo but seems like she's not here, so he can check offline with design later 19:49:49 unless there's anyone else from design? 19:50:07 or anything anymone needs from Design for Beta I should ask for? 19:50:12 mizmo's off with her child I believe (fever) 19:50:21 aha :( 19:50:59 #topic Open floor 19:51:12 jreznik: no websites? 19:51:27 but we are all set 19:51:28 robyduck: oh, sorry! 19:51:31 no worries 19:51:34 #undo 19:51:34 Removing item from minutes: 19:51:39 #topic Websites 19:51:47 Beta websites are all set and ready to go ;) 19:51:48 I knew I missed something 19:51:51 :-) 19:52:05 we are already working on final websites 19:52:07 robyduck: but we listened and added one week for you for GA :) 19:52:20 #info Beta websites are all set and ready to go 19:52:24 jreznik: yeah I saw that, one week more is welcome, yes 19:52:38 the new spins web is for Beta or final? 19:52:48 they are all for final 19:52:59 ok 19:53:01 we will have at least 2 websites to do 19:54:10 jreznik: I don't have anything else 19:54:22 thanks robyduck! 19:54:28 #topic Open floor 19:54:39 so now for open floor? anyone anything? 19:55:08 if not, I'm setting fuse 19:55:09 * roshi has nothing 19:55:10 3... 19:55:19 as always, thanks to you jreznik for 3 hours of chairing 19:55:37 +1 19:55:42 jreznik++ 19:55:43 randomuser: You have already given 1 karma to jreznik 19:55:50 jreznik++ 19:55:51 thanks jreznik 19:55:51 jreznik+++ 19:55:57 jreznik++ 19:56:03 jreznik++ for all the things you do. ;) 19:56:05 robyduck: :D I still have to update schedule for you but I already dream about my bed :))) 19:56:12 jreznik++ 19:56:25 lol, you deserve it today 19:56:28 ooh, that much, thanks a lot! 19:56:43 jreznik++ 19:56:43 robyduck: You have already given 1 karma to jreznik 19:56:46 uff 19:56:52 jreznik++ 19:56:55 zodbot-- 19:56:58 2... 19:57:23 don't mess with karma! 19:57:25 1... 19:57:59 ok, thanks again for coming - let's hope we will be in a better state next week and ready to release! 19:58:03 #endmeeting