Fedora 27 Change Checkpoint: Completion deadline (testable)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Greetings!

Today, on 2017-Aug-01, we have reached Fedora 27 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 on
2017-Aug-04 meeting. Contingency plan for System Wide Changes in case
of serious doubts regarding Change completion, will be activated.

Side note: Currently we still have several Changes waiting for FESco
approval [4]. I am going to ask FESCo to consider postponing of this
Checkpoint for these Changes, in case these are approved.

[1] https://fedoraproject.org/wiki/Releases/27/Schedule
[2] https://fedoraproject.org/wiki/Releases/27/ChangeSet
[3] http://red.ht/2vijerN
[4] https://pagure.io/fesco/issues

-- 
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux