This message is a reminder that Fedora 23 Change Checkpoint: Completion deadline (testable) is on 2015-07-28 [1].

At this point, all accepted Changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Completion deadline.

This bug should be set at least to the MODIFIED state to indicate that it achieved completeness. Status will be provided to FESCo right after the deadline. If, for any reasons, your Change is not in required state, let me know and we will try to find solution. For Changes you decide to cancel/move to the next release, please use the NEW status and set needinfo on me and it will be acted upon. 

In case of any questions, don't hesitate to ask Wrangler (jkurik). Thank you.

[1] https://fedoraproject.org/wiki/Releases/23/Schedule

This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Removing from the scope of F23 as we have already passed the deadline when this change needs to be in MODIFIED state.

Updating the targeted version of this upgrade. The Node.js SIG is going to work on moving to the 4.x LTS version in the Fedora 24 timeframe.

New WIP Change Proposal: https://fedoraproject.org/wiki/Changes/NodeJS4x

Packages are now all built in the f24-nodejs4 side-tag and it has been requested to be merged back into Rawhide.

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. Additionally, if a change is to be enabled by default, it must be so enabled at Change Completion deadline.

Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness.

Incomplete and non testable Changes will be reported to FESCo on 2016-Feb-26 meeting.  Contingency plan for System Wide Changes, if planned for Alpha (or in case of serious doubts regarding Change completion), will be activated.

This was merged back into Fedora Rawhide several weeks ago. I forgot to update the status to MODIFIED. I have now done so.

At today's FESCo meeting today, we agreed to allow Node.js to ship the 5.x version in Fedora 24. Updating the topic.

I have added release notes text (mainly taken from the change description) to the draft F24 Release Notes here: https://git.fedorahosted.org/cgit/docs/release-notes.git/plain/en-US/Development_Web.xml

Please would you take a look at the draft and let me know if anything should be added or changed.

On 2016-Apr-19 we reached the "Change Checkpoint: 100% Code Complete Deadline" milestone for Fedora 24 release. At this point all the Changes not at least in in "ON_QA" state should be brought to FESCo for review. Please update the state of this bug to "ON_QA" if it is already 100% completed. Please let me know in case you have any trouble with the implementation and the Change needs any help or review.

Thanks, Jan

This is in the stable tree of Fedora 24 already. Marking it as ON_QA, though I'm unclear if this should be closed CURRENT_RELEASE.

(In reply to Stephen Gallagher from comment #11)
> This is in the stable tree of Fedora 24 already. Marking it as ON_QA, though
> I'm unclear if this should be closed CURRENT_RELEASE.

I am going to close all the tracking tickets for delivered Changes after F24 GA. So, you can close the ticket if you feel it is fully implemented and tested, or you can leave it open and it will get closed for you after GA.