Windows Server vNext delayed until 2016

Anybody else thinks it may have something to do with containers support? E.g. Microsoft a) decided that first-class container support is a must, and b) discovered it is hard / disruptive / intrusive to implement, and/or c) is trying to figure out the right thing to do about Kubernetes?