#1550 F24 approved Changes not in MODIFIED status (considered as not testable)
Closed None Opened 8 years ago by jkurik.

Hi FESCo,

on 2016-Feb-23 we have reached Fedora 24 Change Checkpoint: Completion deadline (testable). At this point, all accepted changes should be substantially
complete, and testable. Change tracking bugs should be set to MODIFIED state to indicate it achieved completeness.

The following link is a dynamic Bugzilla query showing all the tracking bugs of approved Changes for F24 which are not in MODIFIED state: [https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&classification=Fedora&columnlist=product%2Ccomponent%2Cversion%2Cbug_status%2Cresolution%2Cshort_desc%2Ckeywords%2Cflagtypes.name&f1=status_whiteboard&list_id=4680417&o1=anywords&product=Fedora&query_based_on=&query_format=advanced&status_whiteboard=ChangeAcceptedF24&status_whiteboard_type=allwordssubstr&v1=SystemWideChange%20SelfContainedChange link]

I would like to ask FESCo to check this list and provide a follow up guidance. From my POV we have the following possibilities:
Delay the "Completion deadline (testable)" milestone for a week or two as we have a spare time till Alpha Freeze. Unfortunatelly, as we have already branched F24 from rawhide, this will cause a need to commit the unfinished work to F24 branch as well as to rawhide.
Activate Contingency plan at least for System Wide Changes


Well, some of these are clearly already available and likely just haven't had their tickets updated. (Hopefully those will be cleared up before the meeting; I just took care of the Node.js one, myself).

Let's get this on the agenda for the FESCo meeting this week and go through each of them. Jan, could you gather a list of the change owners together and invite them to the meeting so they can weigh in?

Replying to [comment:1 sgallagh]:

Let's get this on the agenda for the FESCo meeting this week and go through each of them. Jan, could you gather a list of the change owners together and invite them to the meeting so they can weigh in?

I guess most of the Tracking bugs will be updated till the meeting. So, I will do review of it on Thursday (a day before the FESCo meeting) and I will invite all the Change owners not having Tracking bugs in MODIFIED state.

As of now, the following set of Tracking bugs is not in (at least) MODIFIED state:
1243736 Layered Docker Image Build Service [https://bugzilla.redhat.com/show_bug.cgi?id=1243736#c16 Current status]
1288079 GHC 7.10 [https://bugzilla.redhat.com/show_bug.cgi?id=1288079#c2 Postponed due to lack of manpower]
1288082 Systemd package split [https://bugzilla.redhat.com/show_bug.cgi?id=1288082#c2 Current status]
1301529 NeuroFedora
* 1303542 NewRpmDBFormat [https://bugzilla.redhat.com/show_bug.cgi?id=1303542#c3 Turned into tech-preview]

Owners of these Changes were explicitly requested to update the Tracking bug or join the [https://apps.fedoraproject.org/calendar/fesco/#m53 FESCo meeting] in case the Change is not ready.

The last 2 of these are addressed in ticket #1552, so closing this one in favor of that one.

Login to comment on this ticket.

Metadata