19:00:12 #startmeeting F27 Beta Readiness Meeting 19:00:13 Meeting started Thu Sep 14 19:00:12 2017 UTC. The chair is jkurik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:13 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:13 The meeting name has been set to 'f27_beta_readiness_meeting' 19:00:14 #meetingname f27-beta-readiness-meeting 19:00:14 The meeting name has been set to 'f27-beta-readiness-meeting' 19:00:15 #topic Roll Call 19:00:17 .hello jkurik 19:00:18 jkurik: jkurik 'Jan Kurik' 19:00:42 #chair nirik dgilmore sgallagh adamw mizmo mattdm stickster bexelbie mboddu 19:00:42 Current chairs: adamw bexelbie dgilmore jkurik mattdm mboddu mizmo nirik sgallagh stickster 19:01:00 .hello bex 19:01:01 bexelbie: bex 'Brian (bex) Exelbierd' 19:01:21 * bexelbie is distracted - if I respond late, I am sorry 19:01:28 .hello pfrields 19:01:29 stickster: pfrields 'Paul W. Frields' 19:01:37 bexelbie: ok, thanks for joining 19:01:41 hi stickster 19:01:50 o/ jkurik and all 19:02:01 .hello2 19:02:02 robyduck: robyduck 'Robert Mayr' 19:02:30 hi robyduck 19:02:54 let's start, hopefully more people will join in a while 19:03:03 hi jkurik et all 19:03:12 #topic Purpose of this meeting 19:03:13 #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:03:33 #link https://fedoraproject.org/wiki/Release_Readiness_Meetings 19:03:35 #topic Current status 19:03:36 #info Fedora 27 Beta is No-Go 19:03:44 #info The next Go/No-Go meeting is planned on Thursday, Sep 21st. The Beta release slips for one week however due to “Rain date feature” we are not going to slip the Final GA yet. 19:04:06 #topic Design 19:04:07 The current status we have put together on #fedora-design channel is as follows: 19:04:08 .hello2 19:04:10 bowlofeggs: bowlofeggs 'Randy Barlow' 19:04:21 hello bowlofeggs 19:04:29 #info Wallpapers are still in development process following some critique. This is expected to be solved within 2-3 days. Beside of this, there is no known issue blocking the F27 Beta release. 19:04:29 .hello2 19:04:30 langdon: langdon 'Langdon White' 19:04:30 Mizmo: Would you like to add something ? 19:04:37 hi langdon 19:04:53 hi.. was typing and missed the hour turnover 19:05:04 hey jkurik! 19:05:33 morning 19:05:47 hi nirik 19:05:57 nirik: somewhere.. and probably meh :) 19:06:21 ok, so I consider the status above as "sufficient" for the moment 19:06:27 it's always morning when you enter a irc channel. ;) 19:06:39 #topic Infrastructure 19:06:41 nirik: Any known issues which might block us from releasing F27 Beta ? 19:06:53 except the issues why we are no-go 19:06:56 nope. Should be all ready once we have a approved compose to go with 19:07:22 #info Infrastructure team should be all ready once we have a approved compose to go with 19:07:26 thanks nirik 19:07:38 * mboddu is here 19:07:42 hi mboddu 19:08:02 #topic Ambassadors 19:08:03 robyduck: may I ask you please for the readiness update from Ambassadors POV ? 19:08:05 Is there anything Ambassadors are aware of what might block us from releasing F27 Beta ? 19:08:06 is the current plan for th emodular beta to also be delayed by ~1 month? 19:08:12 yes sure 19:08:14 or just it's final release? 19:08:33 Ambassadors are set, we synched out with other groups to be sure all is in place for GA. Beside of our tasks we keep on doing the next week, there is no blocker for F27 Beta. 19:08:40 bowlofeggs: lets talk about this at the end of the meeting, we probably need mattdm for this discussion 19:08:43 ack 19:09:58 eof 19:10:09 haha 19:10:17 #info Ambassadors are set, synchronized with other groups to be sure all is in place for GA. There is no blocker for F27 Beta from ambassarors' POV. 19:10:25 bowlofeggs: ? 19:10:31 robyduck: thanks 19:10:37 i was laughing at robyduck's eof 19:10:55 #topic Documentation 19:10:56 bexelbie: can you please provide us with readiness status for Documentation ? 19:10:59 not sure why you laugh 19:11:18 * mattdm is here now. sorry 19:11:33 We haven't done any specific work toward F27 19:11:38 we have a dev branch in master 19:11:50 we should begin posting Change tickets soon to get Release notes started 19:11:57 as I understand it we do not have a specific deliverable for the beta 19:12:05 as the release announcement is owned by marketing 19:12:16 * bexelbie is sitting in for randomuser so if I have it wrong, please let me know 19:12:29 we can branch at any point - given the volume of commits there is no rush 19:12:31 eom 19:13:22 robyduck: I think bowlofeggs didn't realize your eof was about the Ambassadors report... it might have meant "eof" was to cut off the modularity discussion :-) 19:13:43 #info The Documentation team haven't done any specific work toward F27 however as there are no specific deliverables for Beta it does not block the release. 19:14:01 stickster: it's ok 19:14:05 actually, i just thought it was a clever way to say "that's all i have to say" 19:14:14 sorry, i didn't meant ot derail us or anything 19:14:16 #info The Design team should begin posting Change tickets soon to get Release notes started 19:14:25 no 19:14:37 Docs has to post change tickets and track down beat writers 19:14:40 Design is not involved 19:14:54 #undo 19:14:54 Removing item from minutes: INFO by jkurik at 19:14:16 : The Design team should begin posting Change tickets soon to get Release notes started 19:15:00 last release we opened a ticket for each change and tracked it down 19:15:06 #info The Documentation team should begin posting Change tickets soon to get Release notes started 19:15:12 (streamlining this is what I want to talk to you about jkurik :) ) 19:15:33 #action bexelbie to reach jkurik and talk to him 19:15:57 bexelbie: thanks 19:16:05 yw 19:16:18 BTW that action is not related to the release 19:16:32 bexelbie: ok 19:16:40 #topic FESCo 19:16:42 nirik, sgallagh, dgilmore, maxamillion, jsmith, kalev,till, bowlofeggs, jforbes: anyone of you wants to speak in the name of FESCo ? 19:17:28 sure, I can... 19:18:06 I think everything is ready for beta from our side. There may still be questions around the modular server schedule, but we can address those soon... no need to hold up beta. 19:18:24 +1 19:18:59 #info Everything is ready for beta from FESCo side. There may still be questions around the modular server schedule, but FESCo can address those soon... no need to hold up beta 19:19:06 nirik: thanks 19:19:23 #topic Marketing 19:19:25 #link https://fedoraproject.org/wiki/F27_Beta_release_announcement 19:19:26 There was an update from mailga sent via email: 19:19:44 For the F27 beta, we're a bit late mainly due to Flock and travels along with the holidays period. 19:19:46 In substance: 19:19:47 1) we don't have reviewed Firefox update, but we will ready in two/three days 19:20:02 #info Firefox update, but we will ready in two/three days 19:20:04 2) we created the talking points wiki page by copy/paste the F26 one. We need the WGs help in order to update it. 19:20:05 #link https://fedoraproject.org/wiki/Fedora_27_talking_points 19:20:07 #action All-WGs are requested to help with update of the Fedora 27 talking points wiki page 19:20:08 #info Fedora 27 talking points in DRAFT version, help from WGs is needed 19:20:25 3) we also created the beta release announce but we didn't solicit WGs bullet points, of course we will be ready for the beta release along with FPL. We strongly need bullet points, otherwise we can only write about something general. 19:20:27 #link https://fedoraproject.org/wiki/F27_Beta_release_announcement 19:20:29 #action All-WGs are requested to help to solicit WGs bullet points. 19:20:30 #info F27 Beta Release Announcement in DRAFT version help from WGs is needed 19:20:45 Anyone from Marketing team wants to comment on this update ? 19:21:13 * stickster will help pull together bullet points for Workstation WG. 19:21:40 stickster++ 19:21:40 jkurik: Karma for pfrields changed to 15 (for the f26 release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:22:01 moving on ... 19:22:02 jkurik: Am I correct this is a copy/paste of an F26 Beta announcement? Looks like last release's info 19:22:04 #topic Fedora Engineering Manager 19:22:05 stickster: are you aware of any issue possibly blocking the F27 Beta release, except the missing RC and state of Fedora [Modular] Server ? 19:22:30 jkurik: beyond those issues covered already -- no 19:22:43 stickster: it should be slightly modified F26 version, as far as I understand it 19:22:50 jkurik: thanks 19:22:58 eomo 19:23:03 ha, I can't type well today. eom 19:23:08 ok, thanks for the update 19:23:16 "Other than nothing working, is there anything wrong?" 19:23:23 us old vax people prefer ^Z 19:24:04 * langdon takes to twitter for an OH 19:24:51 haha 19:25:32 lol 19:25:33 aside from that mrs lincoln, how was the play? 19:25:40 haha... ouch. 19:25:44 nirik: ROTFL 19:26:03 we've gotten pretty good at the gallows humor over the years ;-) 19:27:00 yeah 19:27:57 i went to retweet langdon and saw https://twitter.com/internetofshit/status/906640862968406016 19:28:24 bowlofeggs: that's a lot of extra legroom 19:28:28 I don't see what the big complaint is 19:28:52 and doesn't everyone want to be in the 'cloud' now anyway? 19:29:03 that's direct access right there 19:29:05 haha 19:29:09 looks like I got disconnected for a while 19:29:22 jkurik: we were all telling jokes in your absence, anyway 19:29:28 :) 19:29:34 #info Fedora Engineering Manager is not aware of any blocking issues, beyond those already covered 19:29:36 ‎[21:24] ‎<‎jkurik‎>‎ #topic Fedora Project Leader 19:29:38 if laughter powered the release process the beta would already be out 19:30:13 #topic Release Engineering 19:30:15 dgilmore, mboddu: beside of the fact, there is no RC, is there anything you see as an issue with the F27 Beta readiness ? 19:31:06 jkurik: nope, and the questions around fedora modular, nothing is blocking us 19:32:01 #info Except the questions around fedora modular server edition, there is nothing what blocks releng from F27 Beta release 19:32:06 mboddu: thanks 19:32:23 #topic Websites 19:32:24 robyduck: may I ask you please for an update ? 19:32:33 yeah, that's me again 19:32:43 so, websites are not really set, but we have some additional time. 19:32:50 right 19:32:53 We are worried about Modular Server, but it seems we have enough time to set up something new if the plan of a 1 month slip for server is the one we will go for. 19:33:30 moreover, we need to fix Docs links, but it seems there is no way from making us work twice, because "current" links are not working and the rest is also not redirectable. 19:33:44 As we have another week at least, I'm not sure if there is still a chance to get "current" links working 19:34:05 anyway, as always we will get all websites running in time, YAY 19:34:05 #info Websites are not really set, but the team have some additional time. The team especially worried about Modular Server. 19:34:29 That's all from me ;) 19:35:00 robyduck: +1 on all the above 19:35:01 thanks robyduck! 19:35:12 #info Docs links needs to be fixed, however as there another week at least till the release there is still a chance to get "current" links working 19:35:21 :) 19:35:38 #info The team will get all websites running in time 19:35:58 thanks robyduck for the update as well as for the Websites care 19:36:03 robyduck++ 19:36:04 YW 19:36:17 #topic Translations 19:36:18 I have received an email from paragan, stating readiness for F27 Beta as follows: 19:36:21 * stickster punches zodbot in the face and sends robyduck all the cookies 19:36:36 I don't think there are any blocker bugs or any issues related to translations in F27. You can consider Translations Team status as ready. 19:36:37 lol 19:36:37 #info Translation team is ready for the F27 Beta release 19:36:44 * puiterwijk keeps stickster away from zodbot 19:36:51 *snicker 19:37:14 #topic CommOps 19:37:15 There are no direct deliverables for the F27 Beta release from CommOps team, however I would like to give a room to team representatives to express their POV. 19:37:16 * robyduck awards stickster with a badge for punching zodbot 19:37:32 anyone from CommOps ? 19:38:16 ok, so moving on ... 19:38:25 and the funny part now ... 19:38:28 #topic Fedora Project Leader & Fedora Modular Server 19:38:54 langdon, mattdm: would you like to update us on the Fedora Modular Server ? 19:39:38 yes! 19:39:51 So, we had a long discussion about this in the Council meeting yesterday 19:40:03 mattdm and i both having laggy network 19:40:04 * langdon points at mattdm to start 19:40:11 the result of which was that while we don't feel like we can put the rest of the release at risk by blocking on it 19:40:22 we *also* feel like it's incredibly important to the future of Fedora 19:40:46 so we're asking to alter the contingency plan so that it is released on a separate schedule from the GA 19:41:06 * langdon realizes that probably means he should update the wiki page 19:41:08 We just officially approved that and are sending that request to Server WG and FESCo 19:41:17 and many details need to be worked out 19:41:32 but the upshot here is that we should not block the GA release on Modular Server 19:41:55 (what exactly should happen with blocking on Fedora Server As It Is Now for F27 is still TBD, I think) 19:41:57 for f27.. like this is a one off 19:42:23 although also, what to do in the future remains an open question. We may turn out to *like* the split release 19:42:39 I have a theory that we can get more attention for Fedora Server in general by announcing it separately 19:42:43 I would also add, our goal is to hit beta the same as workstation and cloud.. this is only if we can't 19:42:44 and here's a chance to find out :) 19:43:38 * nirik is fine with that plan, but thinks we should ship a legacy server for f27... otherwise people will be confused and annoyed. 19:43:56 we are tracking the issues in the modularity project in pagure, i am working on putting them as BZs blocking the change.. 19:43:57 i believe that threebean and mcurlej were not planning to give bodhi the ability to update modules until the freeze is over - is it ok to put out a modular server beta that can't do updates yet? 19:44:13 bowlofeggs: no, i don't think so 19:44:25 nirik: We should definitely ship the everything install from which people can build *a* fedora server. 19:44:32 I think we need ot ask threebean et al to go back to the earlier plan of an FBR 19:44:44 langdon: ok - i'll chat with them about that 19:44:49 bowlofeggs: thanks 19:44:56 From my informal survey earlier, there's a *lot* more of that than Fedora Server As Edition As Designed 19:45:16 mattdm: "that"? 19:45:20 #info As Fedora Council does not want to put the rest of the release in risk and Council *also* feel like it's incredibly important to the future of Fedora to have Fedora Modular Server released it has been agrred on the Council level to alter the contingency plan so that it is released on a separate schedule from the GA 19:45:21 mattdm: sure, but if people go to the website and see f26 server or nothing, they will then be confused if someone tells them... oh you can download a f27 netinstall and still install things you want 19:45:25 #link https://pagure.io/Fedora-Council/tickets/issue/141 19:45:31 #info Council has officially approved that and are sending that request to Server WG and FESCo 19:45:35 #info There are still many details to be worked out 19:45:54 mic drop from jkurik 19:46:16 nirik: Yeah, I agree. I think we need a messaging page. I'm gonna work on that. 19:46:19 nirik: i think it would say "coming soon".. do we have a page somewhere about building "something" from the everything repo? 19:46:37 hmm.. IRC does not like my copy/paste updates :-( 19:46:43 * langdon goes off to add another ticket.. at least i get to assign it to mattdm 19:47:12 #info As Fedora Council does not want to put the rest of the release in risk and Council *also* feel like it's incredibly important to the future of Fedora to have Fedora Modular Server released it has been agrred on the Council level to alter the contingency plan so that it is released on a separate schedule fro 19:47:32 #link https://pagure.io/Fedora-Council/tickets/issue/141 19:47:51 #info Council has officially approved that and are sending that request to Server WG and FESCo 19:48:06 #info There are still many details to be worked out 19:48:30 mattdm: is the #info OK or did I missed something while being disconnected ? 19:48:44 jkurik: only missed more jokes :) 19:48:46 looks good to me 19:48:48 :) 19:49:07 ok, so then we are done for this meeting 19:49:16 #topic Open Floor 19:49:33 anything else anyone would like to discuss ? 19:49:36 thanks jkurik! 19:49:39 jkurik: thank you for once again chairing this meeting in your evening time :-) 19:49:56 thanks all 19:50:13 now let's get this Beta off its keister 19:50:30 Thank you all 19:50:39 #endmeeting