openstack team mailing list archive

[Soren Hansen <soren@xxxxxxxxxxx>]

Apologies if this has already been proposed, but how about an option 3
(perhaps more accurately option 2.5):

We already have a process for maintaining code in one project and
occasionally copying it to another project. Namely, code is maintained
in openstack-common and then -- at appropriate times -- gets copied to
Nova or Glance or whatever. Correct?

Seeing as Cinder is supposedly a straight copy of Nova volume, it seems
feasible to occasionally copy it all back into Nova. This way, it's not
a matter of "fixing bugs (and adding features and whatever) twice", but
rather fixing bugs (and adding features and whatever) once and the rest
is straight-forward (possibly even easily scriptable) patch management.

Obviously, this wouldn't happen indefinitely, but simply serve to bridge
the gap between those who want to split it out (with which I can
certainly sympathise) and those who want to keep it Nova for Folsom
(which I can also sort of relate to).

-- 
Soren Hansen             | http://linux2go.dk/
Senior Software Engineer | http://www.cisco.com/
Ubuntu Developer         | http://www.ubuntu.com/
OpenStack Developer      | http://www.openstack.org/