==============================================
#fedora-meeting-1: F24 Final Readiness Meeting
==============================================


Meeting started by jkurik at 19:00:16 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-06-09/f24-final-readiness-meeting.2016-06-09-19.00.log.html
.



Meeting summary
---------------
* Roll Call  (jkurik, 19:00:32)

* Purpose of this meeting  (jkurik, 19:03:24)
  * 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)
  * LINK: https://fedoraproject.org/wiki/Release_Readiness_Meetings
    (jkurik, 19:03:34)

* Current status  (jkurik, 19:03:40)
  * Decision from the Fedora 24 Final Go/No-Go meeting is No-Go
    (jkurik, 19:04:15)
  * Due to present blockers and subsequently missing RC compose the
    Final release has been postponed for one week  (jkurik, 19:04:33)
  * The next Go/No-Go meeting is planned on Thursday, June 16th
    (jkurik, 19:04:41)

* Design  (jkurik, 19:05:24)

* Infrastructure  (jkurik, 19:07:55)
  * Infrastructure is ready, no know issues.  (jkurik, 19:08:42)

* Ambassadors  (jkurik, 19:08:52)
  * Ambassadors are ready for the release.  (jkurik, 19:11:52)

* Documentation  (jkurik, 19:12:10)

* FESCo  (jkurik, 19:14:11)
  * There is nothing known what might be blocking from fesco's view
    (jkurik, 19:15:36)

* Fedora Engineering Manager  (jkurik, 19:15:51)
  * There is nothing blocking from Fedora Engineering Manager POV
    (jkurik, 19:18:10)

* Fedora Project Leader  (jkurik, 19:18:28)
  * Fedora Project Leader is ready for F-24 Final release  (jkurik,
    19:19:49)

* Marketing  (jkurik, 19:19:56)
  * 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)
  * 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)

* QA  (jkurik, 19:21:01)
  * QE is ready to start verification of an RC compose once one is ready
    (jkurik, 19:21:45)

* Release Engineering  (jkurik, 19:21:56)
  * Release Engineering is ready, just waiting for that last blocker fix
    to make an RC  (jkurik, 19:22:41)

* Websites  (jkurik, 19:23:04)
  * there are some pending tasks for F24 GA, but the team is confident
    to have it done on time  (jkurik, 19:25:01)
  * the team is ready for F24, just needs to sync out with releng for
    the last updates  (jkurik, 19:25:31)

* Translations  (jkurik, 19:25:44)
  * The Translations team is not aware of any problems  (jkurik,
    19:26:55)

* Design  (jkurik, 19:27:09)
  * 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)
  * the Design team is ready  (jkurik, 19:29:10)

* CommOps  (jkurik, 19:29:37)
  * AGREED: CommOps is ready for Fedora 24 release. None of our current
    activities would block F24.  (jflory7, 19:29:45)

* Documentation  (jkurik, 19:30:19)
  * The documentation should be OK for the release  (jkurik, 19:31:29)

* Open floor  (jkurik, 19:32:26)

Meeting ended at 19:38:04 UTC.




Action Items
------------





Action Items, by person
-----------------------
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* jkurik (96)
* jflory7 (13)
* zodbot (12)
* nirik (10)
* robyduck (6)
* stickster (4)
* adamw (3)
* randomuser (3)
* mizmo (3)
* puiterwijk (2)
* potty (1)
* coremodule (1)
* linuxmodder (1)
* veon (1)
* mattdm (0)
* dgilmore (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot