This is a tracking bug for Change: Atomic Developer Mode
For more details, see: https://fedoraproject.org//wiki/Changes/Atomic_Developer_Mode
Add a "Developer Mode" boot menu entry in the Atomic image to allow users to boot without setting up cloud-init.
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.
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.
AFAICT, I can't test this because we're not currently building F24 Atomic images with F24 content, is that correct?
As a test, looking at the latest compose, the Fedora-Atomic-24 image greets me with a F25/rawhide build. (Whereas the Fedora-Cloud-Base-24 image is correct).
Or is there an F24 two-week release stream being published somewhere else?
Hopefully Kushal will know the right answer for this.
Looks like here is the answer about F24 Atomic Images: https://firstname.lastname@example.org/message/6LUVFAPRWPGFVFOZ5X7IXE5Q4V636UY3/
Thanks for the link Jan. I answered to that email on the list here:
Hopefully someone can clear this up.
Looks like this was fixed recently, so I'll be able to test it soon.
Change working mostly fine. There are some issues that have already been addressed in this update:
which I'm hoping will make it in before the Beta Release.
Will just put this in ON_QA.