#fedora-meeting-1: F24 Final Readiness Meeting

Meeting summary

1. Roll Call (jkurik, 19:00:32)
   
2. Purpose of this meeting (jkurik, 19:03:24)
   1. 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. (jkurik, 19:03:30)
   2. https://fedoraproject.org/wiki/Release_Readiness_Meetings (jkurik, 19:03:34)
   
   
3. Current status (jkurik, 19:03:40)
   1. Decision from the Fedora 24 Final Go/No-Go meeting is No-Go (jkurik, 19:04:15)
   2. Due to present blockers and subsequently missing RC compose the Final release has been postponed for one week (jkurik, 19:04:33)
   3. The next Go/No-Go meeting is planned on Thursday, June 16th (jkurik, 19:04:41)
   
   
4. Design (jkurik, 19:05:24)
   
5. Infrastructure (jkurik, 19:07:55)
   1. Infrastructure is ready, no know issues. (jkurik, 19:08:42)
   
   
6. Ambassadors (jkurik, 19:08:52)
   1. Ambassadors are ready for the release. (jkurik, 19:11:52)
   
   
7. Documentation (jkurik, 19:12:10)
   
8. FESCo (jkurik, 19:14:11)
   1. There is nothing known what might be blocking from fesco's view (jkurik, 19:15:36)
   
   
9. Fedora Engineering Manager (jkurik, 19:15:51)
   1. There is nothing blocking from Fedora Engineering Manager POV (jkurik, 19:18:10)
   
   
10. Fedora Project Leader (jkurik, 19:18:28)
    1. Fedora Project Leader is ready for F-24 Final release (jkurik, 19:19:49)
    
    
11. Marketing (jkurik, 19:19:56)
    1. Marketing is ready for Fedora 24. Release announcement is in progress between mattdm, decause, jzb, and bkp. Fedora Magazine working on posts for F24 announcement, what's new in F24, and upgrading from F23 => F24. (jflory7, 19:20:05)
    2. HELP: Anyone with strong familiarity with the upgrade process (via dnf) would be appreciated to read the upgrading guide article for technical accuracy. Please visit #fedora-mktg if you can help with a quick read. (jflory7, 19:20:09)
    
    
12. QA (jkurik, 19:21:01)
    1. QE is ready to start verification of an RC compose once one is ready (jkurik, 19:21:45)
    
    
13. Release Engineering (jkurik, 19:21:56)
    1. Release Engineering is ready, just waiting for that last blocker fix to make an RC (jkurik, 19:22:41)
    
    
14. Websites (jkurik, 19:23:04)
    1. there are some pending tasks for F24 GA, but the team is confident to have it done on time (jkurik, 19:25:01)
    2. the team is ready for F24, just needs to sync out with releng for the last updates (jkurik, 19:25:31)
    
    
15. Translations (jkurik, 19:25:44)
    1. The Translations team is not aware of any problems (jkurik, 19:26:55)
    
    
16. Design (jkurik, 19:27:09)
    1. The team is unaware of any design-related issues. The team has made revisions to the wallpaper after alpha feedback and got positive comments on the changes (jkurik, 19:29:00)
    2. the Design team is ready (jkurik, 19:29:10)
    
    
17. CommOps (jkurik, 19:29:37)
    1. AGREED: CommOps is ready for Fedora 24 release. None of our current activities would block F24. (jflory7, 19:29:45)
    
    
18. Documentation (jkurik, 19:30:19)
    1. The documentation should be OK for the release (jkurik, 19:31:29)
    
    
19. Open floor (jkurik, 19:32:26)

Action items

1. (none)

People present (lines said)

1. jkurik (96)
2. jflory7 (13)
3. zodbot (12)
4. nirik (10)
5. robyduck (6)
6. stickster (4)
7. adamw (3)
8. randomuser (3)
9. mizmo (3)
10. puiterwijk (2)
11. potty (1)
12. coremodule (1)
13. linuxmodder (1)
14. veon (1)
15. mattdm (0)
16. dgilmore (0)