#fedora-meeting: F24 Alpha Readiness Meeting

Meeting summary

1. Roll Call (jkurik, 19:00:25)
   
2. Purpose of this meeting (jkurik, 19:03:22)
   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:35)
   2. https://fedoraproject.org/wiki/Release_Readiness_Meetings (jkurik, 19:03:37)
   
   
3. Current status (jkurik, 19:03:48)
   1. Fedora 24 Alpha is No-Go (jkurik, 19:03:50)
   2. Due to present blockers the Alpha release has been postponed (jkurik, 19:03:51)
   3. The next Go/No-Go meeting is planned on Wednesday, March 23rd (jkurik, 19:03:53)
   
   
4. Design (jkurik, 19:04:45)
   1. design team is good for alpha (jkurik, 19:06:17)
   
   
5. Infrastructure (jkurik, 19:06:55)
   1. Infrastructure team is all set. There is a storage upgrade planned for alpha release day, but nirik is asking them to move it. (jkurik, 19:07:59)
   
   
6. Ambassadors (jkurik, 19:08:17)
   1. Ambassadors have not discussed the readiness for Alpha, however each region have everything set. (jkurik, 19:10:34)
   
   
7. Documentation (jkurik, 19:10:56)
   1. ACTION: jkurik to check offline whether the Documentation team is ready for F24 Alpha release (jkurik, 19:14:01)
   
   
8. FESCo (jkurik, 19:14:18)
   1. FESCo sees no blockers and should be good to go... (jkurik, 19:15:26)
   
   
9. Fedora Engineering Manager (jkurik, 19:15:48)
   
10. Fedora Project Leader (jkurik, 19:18:07)
    
11. Fedora Engineering Manager (jkurik, 19:18:42)
    1. Fedora Engineering Manager has no pending items in his area that would delay the release (jkurik, 19:19:43)
    
    
12. Fedora Project Leader (jkurik, 19:19:57)
    
13. Marketing (jkurik, 19:22:27)
    1. no blockers from the releas but Marketing is trying to generate talking points of all the "new things" in F24 from the Editions and Spins.Workstation + Cloud should be set, but they still need to gather info from Server and the Spins. (jkurik, 19:24:32)
    2. People having info about F24 Server changes are requested to contribute (jkurik, 19:25:09)
    3. https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/4RROCC2M6NAKLBRESLZ5DDA6PPEVKE63/ (jkurik, 19:25:17)
    4. ACTION: jflory7 Follow up with mattdm about creating the F24 Alpha announcement on the Fedora Magazine (jflory7, 19:26:45)
    
    
14. QA (jkurik, 19:27:07)
    1. QE is more or less on top of things. Alpha 1.5 test coverage is nearly complete, only missing Server tests. (jkurik, 19:28:33)
    2. QE is doing a lot of work behind the scenes to keep the validation process working , but that should all be mostly done by now and stuff is...mostly working (jkurik, 19:29:23)
    
    
15. Release Engineering (jkurik, 19:30:03)
    
16. Documentation (jkurik, 19:33:13)
    1. Documentation is just getting started. However there is no blocking issue for F24 Alpha at the moment. (jkurik, 19:36:49)
    
    
17. Translations (jkurik, 19:37:06)
    1. Software String Freeze happened with Alpha freeze i.e. on 2016-03-08. The team have just started doing translations. (jkurik, 19:38:14)
    2. The team sees no issues to go live with the Alpha (jkurik, 19:38:45)
    
    
18. Websites (jkurik, 19:39:37)
    1. websites are all in a good shape, however the team needs to sync out with releng to fix paths and checksums (jkurik, 19:40:56)
    2. The Websites team welcomes testers (jkurik, 19:41:46)
    
    
19. Scheduling of the Release time (jkurik, 19:42:12)
    1. ACTION: jkurik to get F24 Alpha readiness status from mattdm (FPL) and dgilmore (RelEng) (jkurik, 19:49:01)
    2. ACTION: jkurik to follow up with release time via ML (jkurik, 19:49:23)
    3. ACTION: jflory7 For Magazine, F24 Alpha release: Unless release time changes, intend to schedule near 14:00 UTC (jflory7, 19:49:39)
    
    
20. Fedora Project Leader (jkurik, 19:51:51)
    1. Fedora Project Leader will make sure to be ready for next week with the annoucement (jkurik, 19:53:25)
    
    
21. Open floor (jkurik, 19:58:34)
    
22. CommOps (jkurik, 19:59:17)
    1. CommOps has no blockers for F24. The team has a lot on ongoing tasks to improve some areas in time for the full release of F24.The major focus right now is looking at Onboarding and building a strategy for the different sub-projects across Fedora with Badges. (jkurik, 20:02:48)
    
    
23. Open floor (jkurik, 20:03:16)

Action items

1. jkurik to check offline whether the Documentation team is ready for F24 Alpha release
2. jflory7 Follow up with mattdm about creating the F24 Alpha announcement on the Fedora Magazine
3. jkurik to get F24 Alpha readiness status from mattdm (FPL) and dgilmore (RelEng)
4. jkurik to follow up with release time via ML
5. jflory7 For Magazine, F24 Alpha release: Unless release time changes, intend to schedule near 14:00 UTC

Action items, by person

1. jflory7
   1. jflory7 Follow up with mattdm about creating the F24 Alpha announcement on the Fedora Magazine
   2. jflory7 For Magazine, F24 Alpha release: Unless release time changes, intend to schedule near 14:00 UTC
2. jkurik
   1. jkurik to check offline whether the Documentation team is ready for F24 Alpha release
   2. jkurik to get F24 Alpha readiness status from mattdm (FPL) and dgilmore (RelEng)
   3. jkurik to follow up with release time via ML
3. mattdm
   1. jflory7 Follow up with mattdm about creating the F24 Alpha announcement on the Fedora Magazine
   2. jkurik to get F24 Alpha readiness status from mattdm (FPL) and dgilmore (RelEng)

People present (lines said)

1. jkurik (120)
2. jflory7 (22)
3. zodbot (16)
4. stickster (14)
5. robyduck (14)
6. randomuser (8)
7. mattdm (8)
8. nirik (7)
9. pravins (6)
10. adamw (4)
11. potty (4)
12. mizmo (2)
13. b10n1k (1)
14. bowlofeggs (1)