A continuous delivery build is about setting up the necessary checks to make sure that a "snapshot" is in a good enough state to be released (from a releng perspective).
If we have this, then it means that planning can be changed to whatever strategy; without requiring any specific effort to adapt.

I bootstrapped a CI job to start "hosting" all those quality checks: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/devstudio-isGoodForRelease_master/