Fedora 26 Change Checkpoint: Completion deadline (testable)
Greetings!
Today, on 2017-Feb-28, we have reached Fedora 26 Change
Checkpoint:Completion deadline (testable) [1].
At this point, all accepted changes [2] should be substantially
complete, and testable. Additionally, if a change is to be enabled by
default, it must be enabled at Change Completion deadline as well.
Change tracking bug should be set to the MODIFIED state to indicate it
achieved completeness.
Incomplete and non testable Changes [3] will be reported to FESCo for
2017-Mar-03 meeting. Contingency plan for System Wide Changes, if
planned for Alpha (or in case of serious doubts regarding Change
completion), will be activated.
Side note: Currently we still have two Self-Contained Changes waiting
for FESco approval [4]. I am going to ask FESCo to consider postponing
of this Checkpoint for these two Changes if these are approved.
[1] https://fedoraproject.org/wiki/Releases/26/Schedule
[2] https://fedoraproject.org/wiki/Releases/26/ChangeSet
[3] http://red.ht/2ltXbqk
[4] https://pagure.io/fesco/issue/1635#comment-350632
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic