19:01:33 #startmeeting F29 Final Readiness Meeting 19:01:33 Meeting started Thu Oct 18 19:01:33 2018 UTC. 19:01:33 This meeting is logged and archived in a public location. 19:01:33 The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:33 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:01:33 The meeting name has been set to 'f29_final_readiness_meeting' 19:01:35 #meetingname f29-Final-readiness-meeting 19:01:35 The meeting name has been set to 'f29-final-readiness-meeting' 19:01:40 #topic Roll Call 19:01:54 .hello psabata 19:02:05 contyk: psabata 'Petr Šabata' 19:02:48 morning 19:03:01 * stickster lurks, in another meeting 19:04:26 well the attendance here seems to roughly correspond to our readiness to release :-) 19:04:32 .hello2 19:04:35 frantisekz: frantisekz 'František Zatloukal' 19:04:36 :D 19:05:07 .hello ngompa 19:05:08 Pharaoh_Atem: ngompa 'Neal Gompa' 19:05:21 okay, i'll get started and we'll see who else shows up 19:05:24 #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:05:26 #link https://fedoraproject.org/wiki/Release_Readiness_Meetings 19:05:32 #topic Current status 19:05:40 #info Fedora 29 Final is NO-GO 19:05:41 #info The next Go/No-Go meeting is planned on Thursday, 2018-10-25 19:05:43 #info The Final release moves from preferred target date to target date #1, which is 2018-10-30 19:05:54 any questions on F29 status? 19:06:29 is it supergreen? 19:06:31 #info We will NOT repeat this meeting after next week's Go/No-Go meeting 19:06:58 it's super...something 19:07:13 okay, time to go around 19:07:18 #topic Ambassadors 19:08:34 any readiness update from the Ambassadors? 19:09:12 #topic Cloud WG 19:09:19 any readiness update from the Cloud WG? 19:10:33 #topic Design 19:10:41 any readiness update from Design? 19:11:25 this is fun 19:11:32 i am having a blast :-) 19:11:33 #topic Desktop 19:11:44 any readiness update from Desktop WG? 19:12:23 If they aren't here, they must be ready right? right? 19:12:29 exactly! 19:12:33 #topic Documentation 19:12:40 any readiness update from the Documentation team? 19:13:19 we still need to write most of the release notes (contributions appreciated!) but we can make it for the release 19:13:37 #help Release Notes contributions needed 19:13:43 #info Docs is ready for the release 19:13:47 pbokoc++ 19:13:47 bcotton: Karma for pbokoc changed to 7 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:14:05 any questions or comments for docs team? 19:15:32 #topic Fedora Project Leader 19:15:39 any readiness update from mattdm? 19:16:21 #topic FESCo 19:16:30 yay 19:16:36 should be all ready for release as far as I know... 19:16:37 .fesco 2001 19:16:39 contyk: Issue #2001: F29 Final: dnf rebase requested post-freeze - fesco - Pagure.io - https://pagure.io/fesco/issue/2001 19:16:42 #info yay 19:16:44 there is this 19:16:46 oh right that. 19:16:56 I asked people to vote in ticket... 19:17:15 I haven't yet but I'm going to be +1 to the rebase 19:17:34 #info FESCo is voting on whether to accept a dnf rebase 19:17:45 #link https://pagure.io/fesco/issue/2001 19:18:29 any questions or comments for FESCo? 19:19:00 i will say that we're trying to have some conversations about how to prevent last-minute major dnf changes in the future, so there's that 19:19:41 bcotton: mattdm not ready at all! 19:19:52 my understanding of the version bump to 4.0 is purely political 19:20:02 * mattdm promises to be ready next week for realz though 19:20:05 mattdm: well then good news. Fedora's not ready for you to be ready :-) 19:20:25 my finely-honed procrastination instincts were right on the money 19:20:41 and as the packager of the DNF stack in other distributions, I can pretty much confirm that the churn between 3.6 to 4.0 is no different than the various 3.x point releases have been thus far 19:20:59 right. but thats still not ideal/what we want 19:21:14 I didn't say it's a *good* thing that it churns so much between point releases 19:21:26 what we want is specific patches only for those issues we want patches for. Nothing else. But such is life sometimes. 19:21:42 so far, we've been accepting releases as such anyway, so *shrugs* 19:22:43 let's move on to infra 19:22:48 #topic Infrastructure 19:23:05 Should be all ready once we have final bits to distribute. 19:23:20 #info Infra is ready once there are artifacts to deliver 19:23:32 We also have a cloudfront mirror that should be ready for release time. :) 19:24:08 * stickster is now less lurking and will wait for after Marketing's turn to ask a question. 19:24:29 * cverna wait for Marketing's turn too :) 19:24:31 * bcotton thinks he knows what stickster is going to ask :-) 19:24:33 * mboddu is back now 19:24:39 anything else for the infra team? 19:25:35 #topic Marketing 19:26:00 stickster: all yours 19:26:29 bt0 and x3mboy are both away 19:26:29 * stickster waits, since he doesn't represent the Marketing team -- anyone here from that team? 19:27:26 looks like no one's here from Marketing, but we can get your questions and comments on the record anyway 19:27:27 Ah, OK. Well, I only wanted to ask about status of the official announcement. We have a placeholder post on the Fedora Magazine that awaits content. The authorship is assigned to mattdm, per usual, but that needn't block content from other folks. 19:27:51 stickster: afaik no progress has been made on the announcement content, but i'll check 19:28:00 last time they were asking for talking points 19:28:09 it didn't feel like they were getting [m]any 19:28:10 #action bcotton to follow up with Marketing team on Release Announcement content 19:28:20 contyk: that's a fair summary 19:28:34 stickster: I absolutely promise to not wait until last minute :) 19:28:35 I would like to also point out that Fedora Core 1 was released November 6th 15 years ago. we could choose to have a preferred release date of November 6th for Fedora 29 that would be quite nice 19:28:47 cverna++ 19:28:47 frantisekz: Karma for cverna changed to 28 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:28:52 cverna++ 19:28:52 mattdm: Karma for cverna changed to 29 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:28:59 cverna: it's not out of the question :-) 19:28:59 There's quite a bit more in TPs now than Beta, which is nice. 19:29:00 that, um, may not be by choice :) 19:29:10 lol 19:29:16 XD 19:29:17 or we can slip even if we are ready... :D 19:29:33 no redoing f18 please. ;) 19:29:37 we need swag for 15 years of Fedora :) 19:29:41 cverna: That might actually happen :) 19:30:00 cverna++ 19:30:00 Conan_Kudo: Karma for cverna changed to 30 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:30:02 marketing wise it is better to say that we choose it :) 19:30:10 cverna++ 19:30:10 bcotton: Karma for cverna changed to 31 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:30:11 cverna: Haha :) 19:30:14 cverna++ 19:30:25 cverna: that's why we have a preferred target date and target date #1 ;-) 19:30:51 okay, anything else marketing-related? 19:31:03 well, another interesting point 19:31:04 If we slip the rain date, we can give that reason (Its not a slip, we just decided to release on the same date as Fedora Core 1) 19:31:20 Oct 31, 1994 was the Red Hat Linux 0.9 beta release 19:31:31 eof here, you're free to go ahead bcotton 19:31:56 #topic QA 19:32:34 any updates from QA? 19:33:06 nothing serious... just saying something so it doesn't look like QA don't care about meetings... :D 19:33:21 #info QA is testing 19:33:26 frantisekz++ 19:33:36 questions or comments for QA? 19:33:56 looking forward to the RC? 19:34:53 we're doing what we can to sort out all the blockers and to request RC :) 19:35:07 #topic Release Engineering 19:35:15 Releng is *almost* ready 19:35:22 We have pungi config PR waiting, we are testing some changes in Silverblue. 19:35:22 Based on that we will either update the PR or merge it as it is. 19:35:47 #info Releng is almost ready, except for pungi config PR (testing in progress) 19:36:03 questions or comments for releng? 19:36:20 Waiting for the RC request, thats it 19:36:49 #topic Server WG 19:37:42 any readiness updates from Server WG? 19:38:17 Nothing blocking server that I am aware of... its a pretty quiet release for server 19:38:35 quiet is good :-) 19:39:04 the best TP 19:39:38 any questions or comments for Server? 19:40:15 #topic Spins 19:40:27 any readiness updates from Spins WG? 19:40:56 * stickster notes, other than an update of Xfce version for that spin, no others have contributed any content to talking points. 19:41:16 #help Spins need to contribute to talking points 19:42:08 #topic Translations 19:42:16 any readiness updates from translators? 19:43:11 nada 19:43:16 #topic Websites 19:43:25 any readiness updates from websites? 19:44:27 #topic Open floor 19:44:38 anyone I didn't call on or any general topics? 19:44:44 such a big open floor 19:44:59 bcotton: curiosity Q 19:45:04 * contyk waves the Modularity WG flag 19:45:10 bcotton: Do you know the status of IoT content for the website? 19:45:16 contyk: d'oh, sorry. standby 19:45:33 stickster: i do not. i have an action item from yesterday's IoT meeting to follow up on that. thanks for the reminder 19:45:34 * stickster can hold question until Modularity is done 19:45:42 bcotton: oh OK -- thanks. 19:45:57 #topic Modularity 19:46:15 relrod was working on IoT content this morning 19:46:26 so the modulemd dnf database isn't going to make it this release, whis still makes us sad 19:46:35 but currently we're dealing with 19:46:38 .bug 1632518 19:46:39 contyk: Bug 1632518 – PackageKit installs packages from default module streams, but does not enable the module stream - https://bugzilla.redhat.com/1632518 19:46:43 contyk: what's the impact of not having that db 19:46:54 if this doesn't get resolved, we will have to drop the defaults in f29 19:47:32 bcotton: not having the db means your system might get into inconsistent/broken state in some scenarios when the repodata for your installed packages are not available 19:47:53 .bug 1616167 19:47:55 contyk: Bug 1616167 – dnf doesn't record modular metadata in a local database - https://bugzilla.redhat.com/1616167 19:47:59 this is an example, a former blocker ^ 19:48:09 eek. is that the one where it's not getting fixed until january? 19:48:15 yes. :-( 19:48:43 #info modulemd dnf database will not make it into F29 19:49:52 I don't have more details on the current status of the PackageKit issue but it's being worked on 19:50:02 I think that's all from me 19:50:24 any other questions or comments for Modularity? 19:50:30 blek 19:50:52 nirik: is that a question or a comment? :-) 19:51:09 * stickster commends Modularity WG for not trashing the hotel room 19:51:12 that blocker. we need a PK fix asap or something... 19:51:27 * contyk agrees 19:52:15 there's only 2 default streams in 29 right? 19:52:22 yes 19:53:07 and both of those were no longer traditional rpms? 19:53:34 afaik, yes; so people who use these on f28 would need to manually enable those to upgrade 19:54:03 right, but normal f29 wouldn't be too borken by them? it would install from them but not enable them? 19:54:20 anyhow, I am sidetracking... go ahead with the rest of the meeting, we can discuss this in fesco or whatever 19:54:25 you are ;) 19:54:36 anything else for Modularity? 19:54:44 but yes, you could still install them, which is even worse 19:55:00 you'd get modular content on your system without any tools knowing 19:55:47 I'm surprised we were doing *any* default module streams 19:55:55 I don't think anyone expected that for F29 19:56:36 turns out the wording of the change wasn't clear to people who didn't know about it, which is bad 19:57:07 but it was what was meant by it working transparently and such 19:57:14 and I'm a bit concerned that people seem to think retiring dist-git sources is okay for making modules, since you need both... 19:57:35 hm? 19:57:56 there were a number of people suggesting that it's possible to maintain modules without package dist-git 19:58:06 that doesn't sound right 19:58:10 in the interests of wrapping this up, i'm going to move on. let's pick up this conversation elsewhere 19:58:19 +1 19:58:22 #topic Open floor 19:58:33 last call for other items 19:58:45 Hi, sorry im late 19:59:05 welcome x3mboy. want to give a quick update on marketing's readiness? 19:59:30 We are good to go, only issue: spins doesn't have TPs 19:59:57 awesome. stickster called that out earlier so hopefully people notice :-) 20:00:01 #link https://fedoraproject.org/wiki/Fedora_29_talking_points 20:00:33 This should be enough for mattdm to go with a good announcement 20:00:47 great 20:00:49 But it will be nice if some teams add info about spins 20:01:35 (and then complaint about spins not being promoted) 20:01:36 Oooppps 20:01:50 :-D 20:02:13 20:02:25 thanks. any questions or comments for x3mboy? 20:03:35 going 20:03:41 going 20:03:44 gone 20:03:47 #endmeeting