> I didn't mean to make it sound like a business strategy (entirely), I mean it more as a natural progression of how people function. If as an engineer you are

> I didn't mean to make it sound like a business strategy (entirely), I mean it more as a natural progression of how people function. If as an engineer you are spending a lot of time working on Openstack, I'm sure you want to see the new advances and features in the product that you've invested so much time and effort into get into the distro ASAP, as long as they are stable That's not really up to us, though. We still have product managers and project managers and project leaders who decide that Feature XYZ is going into Openstack Zeta, which comes back around to the original issue. If I'm an engineer spending a lot of time working on Openstack, it's likely that I'm spending all of my time (other than hobby projects and side projects) on Openstack, just like you may be spending it on whatever your mainline product is (if you're a dev). All devs probably want to see their features hit stable as soon as possible with wide consumption, but Openstack is a good analogue to Fedora, in the sense that things are operating on a schedule. We aren't releasing new versions of Nova/Neutron/whatever whenever we want or whenever we think it's stable or cool. We try to orchestrate that. Fedora tries to orchestrate projects.