19:00:37 #startmeeting F26 Beta Readiness Meeting 19:00:37 Meeting started Thu May 25 19:00:37 2017 UTC. The chair is jkurik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:37 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:37 The meeting name has been set to 'f26_beta_readiness_meeting' 19:00:47 #meetingname f26-beta-readiness-meeting 19:00:47 The meeting name has been set to 'f26-beta-readiness-meeting' 19:00:47 hello everybody 19:00:56 #topic Roll Call 19:00:57 .hello jkurik 19:00:58 jkurik: jkurik 'Jan Kurik' 19:01:05 .hello mailga 19:01:06 mailga: mailga 'Gabriele Trombini' 19:01:08 #chair nirik dgilmore sgallagh adamw mailga mizmo paragan mattdm stickster bexelbie x3mboy roshi mboddu jflory7 19:01:08 Current chairs: adamw bexelbie dgilmore jflory7 jkurik mailga mattdm mboddu mizmo nirik paragan roshi sgallagh stickster x3mboy 19:01:10 .fas jonatoni 19:01:12 jonatoni: jonatoni 'Jona Azizaj' 19:01:18 morning 19:01:21 .fas x3mboy 19:01:22 x3mboy: x3mboy 'Eduard Lucena' 19:01:26 Hi everyone 19:01:28 morning 19:01:38 .hello roshi 19:01:38 Well, it's afternoon here 19:01:39 roshi: roshi 'Mike Ruckman' 19:01:50 hi :) 19:01:52 .hello veon 19:01:53 veon: veon 'Andrea Masala' 19:01:59 .hello sgallagh 19:02:00 sgallagh: sgallagh 'Stephen Gallagher' 19:02:03 .hello bex 19:02:03 * bexelbie[m] is on mobile 19:02:03 bexelbie[m]: bex 'Brian (bex) Exelbierd' 19:02:27 before we start lets do some formalities... 19:02:30 #topic Purpose of this meeting 19:02:32 #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:02:41 #link https://fedoraproject.org/wiki/Release_Readiness_Meetings 19:02:41 .hello adamwill 19:02:43 adamw: adamwill 'Adam Williamson' 19:02:48 #topic Current status 19:02:58 #info Fedora 26 Beta is No-Go 19:03:04 #info The next Go/No-Go meeting is planned on Thursday, May 1st 19:03:30 June? 19:03:37 .hello duffy 19:03:38 mizmo: duffy 'Máirín Duffy' 19:03:40 #undo 19:03:40 Removing item from minutes: INFO by jkurik at 19:03:04 : The next Go/No-Go meeting is planned on Thursday, May 1st 19:03:46 #info The next Go/No-Go meeting is planned on Thursday, June 1st 19:03:51 bexelbie[m]: thanks 19:04:19 #topic Design 19:04:21 I have seen an email from luya about finished wallpapers/backgrounds, so I expect we are fine... 19:04:26 mizmo: May I ask you please to confirm or update us on the current status ? 19:04:45 * sgallagh will be unable to attend the next Go/No-Go meeting. 19:05:04 sgallagh: we will be missing you 19:05:14 hey jkurik, sure 19:05:20 jkurik: Aim more carefully 19:05:21 so for design, there is a bug that involves a few different parts 19:05:28 we have a freeze exception for it, i'm not 100% sure all the components are in 19:05:34 we have an updated fedora-logos package 19:05:39 an updated f26-backgrounds 19:05:47 and theres a gnome package related to the background overlay plugin for the logo that needs an update too 19:06:02 if you can put the info on what all is required in the bug, that'd be great 19:06:18 i didn't pay that bug any special attention so far, so what's requested for the RC at present is just whatever updates are listed as 'fixing' it 19:06:26 i think fedora-logos doesnt have karma to be autopushed. it was updated tuesday. the f26-backgrounds was updated last friday. i dont know if the gnome stuff was updated yet, its florians bug 19:06:41 mizmo: do you consider these bugs as blocking for the release ? 19:06:50 adamw: ok cool i can list the package versions i know? 19:07:23 mizmo: yeah, in the bug would be great 19:07:25 the bz is 1441844 for reference 19:07:25 jkurik: i wouldn't block it for them no 19:07:26 jkurik: but without them the wallpaper will look off and the logo won't be visible 19:07:27 so it's a visible thing people will notice 19:07:45 sounds like a final blocker 19:07:55 yeah 19:07:56 there's a criterion about 'the intended artwork' or something like that 19:08:06 yeh def a final blocker 19:08:10 #link https://bugzilla.redhat.com/show_bug.cgi?id=1441844 19:08:19 does anybody know what package is involve din the display of the fedora logo? 19:08:58 gnome-shell-extension-background-logo 19:09:10 I think 19:09:45 I don't see any new builds of it tho 19:09:56 thi sis the file we have to change 19:09:59 background-logo-extension-3.22.0-original/schemas/org.fedorahosted.background-logo-extension.gschema.xml background-logo-extension-3.22.0/schemas/org.fedorahosted.background-logo-extension.gschema.xml 19:10:06 er that double pasted, sorry 19:10:22 #info There are some issues with background overlay plugin for the logo. These are not considered as blockers for Beta release however might affect Final release if not solved. 19:10:24 nirik: nope he's waiting on the fedora-logos package to get pushed from testing into stable i guess? because he needs that file to refer to in his xml 19:10:44 ok. could do a buildroot override and push them together... 19:11:03 ok ill mention that in the bug 19:11:34 #info The bug 1441844 already have AcceptedFreezeException to get into the F26 Beta RC compose. 19:12:00 #action mizmo to describe details of these issues in the refferenced bug 19:12:07 thanks mizmo 19:12:34 #topic Infrastructure 19:12:36 nirik: Any known issues which might block us from releasing F26 Beta ? 19:12:47 sure 19:13:08 There is an ongoing slowdown in our storage thats making things slower than normal. Otherwise everything should be ready 19:13:23 There's a ticket out with storage folks and they are looking into that 19:14:21 #info Infrastructure team is experiencing ongoing slowdown in storage thats making things slower than normal. People from the team are already looking into the issue. 19:14:41 #info This is not considered as a blocking issue for the F26 Beta 19:14:53 thanks nirik 19:14:57 no problem. 19:15:07 #topic Ambassadors 19:15:09 jonatoni: may I ask you please for the readiness update from Ambassadors POV ? 19:15:18 Is there anything Ambassadors are aware of what might block us from releasing F26 Beta ? 19:16:07 ah, we have mailga as well 19:16:16 afaik we dont have something that might block the 26 release 19:16:17 We're up to date, there are no blocking issues from the ambassadors side. 19:16:22 right mailga? 19:16:52 that's right. 19:17:09 #info Ambassadors are up to date; there are no blocking issues from the ambassadors side. 19:17:24 ok, thanks, that is fine 19:17:39 #topic Documentation 19:17:50 bexelbie: can you please provide us with readiness status for Documentation ? 19:18:11 Branching is not complete but will be easy to complete. We believe we can publish docs with the correct version number but this needs to be verified. POT files have not been generated but shouldn't be a problem. I don't think this should be a beta blocker, but I don't know what conditions docs blocks for beta. This is a concern for the final release. 19:19:08 This presumes the use of the existing publishing system for F26 and any changes happening for F27 19:19:48 #info Branching and generation of POT files is delayed, however these issues are not considered as blockers for Beta release. These issues will concern for Final release if not fixed. 19:20:06 Did I drop or did my message not transmit? 19:20:12 note, we don't have anything in the criteria about docs at all, really; it's never been considered. 19:20:23 bexelbie[m]: thanks 19:20:51 We should consider adding docs criteria in the future 19:21:20 adamw: it is not in blocker criterias, however according schedule these tasks should be ready for Beta release 19:21:39 so, it is not blocking, but we need to keep an eye on it 19:21:55 well, there can be other processes for blocking stuff than the release criteria, like the fesco exception 19:22:01 just noting we've never considered it in that context 19:22:09 I can't think of many reasons to block the beta on docs. There are a few. 19:22:21 bexelbie[m]: thanks for all the information 19:22:37 You're welcome 19:22:42 #topic FESCo 19:22:45 nirik, sgallagh, dgilmore, jwb, maxamillion, jsmith, kalev, paragan, rathann: anyone of you wants to speak in the name of FESCo ? 19:22:54 no blockers from fesco I am aware of. 19:23:02 erm 19:23:04 \o/ 19:23:37 I have nothing that hasn't been communicated via the standard blocker process 19:23:40 nirik, i agree, but i wonder if resolution on the firefox issue might evolve into a blocker 19:23:47 i honestly can't tell at this point 19:24:07 perhaps. not clear... and I don't think it will by beta... 19:24:16 jwb: it will go through std. blocker process, right ? 19:24:17 i'd like it not to be for beta 19:24:25 jkurik: i suspect so 19:24:42 ok 19:24:54 #info There are no blocking issues FESCo is aware of. 19:24:58 I am not speaking on that topic right now. 19:25:28 what 'firefox issue' is this? 19:26:25 adamw: that it doesn't build on all the arches we support... and it's unclear when it will for some of them 19:26:51 oh, right. we fixed it for the primary arches though, right? 19:26:55 but it does build currently on all the ones we block on, so... 19:26:58 yeah. 19:28:25 * sgallagh leaves to pick up his kid from the bus 19:28:30 #info There are concerns about https://pagure.io/fesco/issue/1707 - we need to watch this, however this is not considered as a blocker for Beta atm. 19:28:36 sgallagh: thanks 19:29:06 nirik, sgallagh, jwb: thanks 19:29:18 #topic Marketing 19:29:20 #link https://fedoraproject.org/wiki/F26_Beta_release_announcement 19:29:27 x3mboy: may I ask you for the Marketing status, please ? 19:30:05 There is no issues in Marketing that can be considered a blocker issue 19:30:16 We are working in the Beta Release announcement 19:30:38 You can preview it here: https://fedoraproject.org/wiki/F26_Beta_release_announcement 19:31:09 The same announcement will be sent to the Magazine to be published when Beta is ready to go 19:31:18 #info The Marketing is working on Beta Release announcement. There are no know issues that can be considered as blockers. 19:31:19 Please feel free to review and comment 19:32:22 #info The Beta Release announcement is going to be publised in as an article Fedora Magazine. A help to review it is appreciated. 19:32:31 x3mboy: thanks 19:32:40 x3mboy++ 19:32:41 mattdm: Karma for x3mboy changed to 28 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:32:52 #topic Fedora Engineering Manager 19:32:54 stickster: are you aware of any issue possibly blocking the F26 Beta release ? 19:33:53 ah, we do not have stickster today. Lets move on I will check off-line 19:34:05 #topic Fedora Project Leader 19:34:06 mattdm: shall we go on with the release, or is there anything you might consider as a blocking issue ? 19:36:51 I believe he may be in a meeting. 19:37:02 Looks like we have lost mattdm for a while. I will move on and return back when mattdm is availabe... 19:37:02 So he blocked from the blocker conversation :) 19:37:23 #undo 19:37:23 Removing item from minutes: 19:37:34 #topic QA 19:37:35 roshi, adamw - anyone can provide us with a readiness update ? 19:38:17 well, aside from having nothing to test, we're fine :) 19:38:29 :) 19:38:58 test coverage on nightlies is looking decent at a glance 19:38:59 Is that an all pass or all fail situation? :) 19:39:06 yeah 19:39:06 we're all set to test an RC when one actually shows up 19:39:11 bexelbie: yes! 19:39:21 until we have a compose, not much we can do 19:39:38 we can always run the tests on the latest validation compose 19:39:44 make sure we have everything covered 19:39:58 #info QA is ready to test F26 Beta RC compose once it is ready. Test coverage on nightlies is looking decent at a glance. 19:40:04 we *are* still missing AD enrolment tests, sigh 19:40:12 adamw, roshi: thanks 19:40:24 np np 19:40:35 #topic Release Engineering 19:40:36 dgilmore, mboddu: beside of the fact, there is no RC, is there anything you see as an issue with the F26 Beta readiness ? 19:41:45 jkurik: Other than no RC we dont have exactly anything else blocking, but we need fixes for the exciting 5 blockers 19:42:35 #info Other than no RC Release Engineering dont have exactly anything else blocking. 19:42:43 mboddu: ok, thanks a lot 19:43:02 #topic Websites 19:43:04 sentairanger, veon: as robyduck is not available, may I ask you please for an update ? 19:43:38 yes, jkurik 19:43:48 no issues for us, websites are ready 19:44:35 for the Beta release obv 19:44:45 #info Websites are ready for the F26 Beta release, no issues so far 19:44:52 veon: excellent 19:44:54 thanks 19:45:08 yw, thanks 19:45:21 #topic Translations 19:45:23 I have received an email from paragan, stating readiness for F26 Beta as follows: 19:45:24 19:45:33 AFAIK there are currently no issues that requires to block the release. Hence you can consider Translation team status as "we are fine". 19:45:35 19:45:45 However paragan also expressed some difficulties the team is facing after noriko has left the team. I will take an action to talk to some people and request a help for the team. 19:46:02 #info Translation team is fine with the F26 Beta release 19:46:04 #action jkurik to help the Translation team with takeover of noriko’s work 19:46:46 Jkurik can you loop me in on that too please 19:46:57 bexelbie[m]: sure 19:47:07 #topic CommOps 19:47:08 There are no direct deliverables for the F26 Beta release from CommOps team, however I would like to give a room to team representatives to express their POV. 19:47:09 It came up in my area earlier and I'd like to work on it together. 19:47:15 Thank you 19:47:30 Is there anyone from the CommOps team to provide an F26 Readiness update of the team ? 19:47:31 bt0dotninja, jflory7: any update ? 19:48:04 I can offer that there are no blockers. The community blog publishing issues are being worked on. 19:49:17 #info Community blog publishing issues are being worked on, however there are no blockers. 19:49:27 bexelbie[m]: thank you 19:49:41 lets check FPL once more ... 19:49:52 #topic Fedora Project Leader 19:50:54 I have received off-line status update from mattdm: 19:50:59 Before the meeting he wrote: jkurik: I'm also going to be in a meeting. FPL status is "good to go; will have even better annoucnements ready for after a week's slip, so that's not all bad" 19:51:00 "good to go; will have even better annoucnements ready for after a week's slip, so that's not all bad" 19:51:33 #info FPL is good to go; will have even better annoucnements ready for after a week's slip, so that's not all bad 19:51:46 so, that is all I guess 19:51:58 #topic Open floor 19:52:00 anything else anyone would like to discuss ? 19:52:17 ! 19:53:03 veon: does it mean you have something ? 19:53:20 yes, once 19:53:23 robyduck, says me: Thanks releng for having the underscore in their conf file 19:53:39 :) 19:53:43 eof 19:53:45 =) 19:54:06 veon: May I ask you please to open a releng ticket for this ? 19:54:23 mboddu: what do you think ? ^^^ 19:54:25 veon: I did a double check of it when I am creating the configs 19:54:36 jkurik: its already correct 19:54:42 ah, great 19:54:56 ah ok :D 19:55:16 looks like we are done for this meeting 19:55:23 enything else ? 19:55:44 Just to thanks the amazing work everybody does for this project! 19:55:50 jkurik++ 19:55:51 x3mboy: Karma for jkurik changed to 6 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:55:59 Thanks for chairing 19:56:05 x3mboy++ 19:56:05 veon: Karma for x3mboy changed to 29 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:56:11 jkurik++ 19:56:11 veon: Karma for jkurik changed to 7 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:56:14 I need to rush out 19:56:19 veon++ 19:56:19 x3mboy: Karma for veon changed to 5 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:56:21 Thank you jkurik for running this. 19:56:48 thanks at all 19:56:57 Thanks everybody for showing up here and all of you for your contribution to the Fedora project. 19:57:04 #endmeeting