Open Stack

Dan Prince <dprince at redhat.com> writes:

> If someone wants to split openstack-common changes into patchsets that
> might be Okay in small numbers. If you are merging say 5-10 changes
> from openstack common into all the various openstack projects that
> could translate into a rather large number of reviews (25+) for things
> that have been already reviewed once.  For me using patchsets to keep
> openstack-common in sync just causes thrashing of Jenkins, SmokeStack,
> etc. for things that have already been gated. Seems like an awful
> waste of review/CI time. In my opinion patchsets are the way to go
> with getting things into openstack-common... but not when syncing to
> projects.
>
> Hopefully this situation is short lived however and we start using a
> proper library sooner rather than later.

Indeed, as a real library, it could be incorporated into the devstack
gate tests like the rest of the libraries, which would simultaneously
gate changes to it using all of the projects that reference it.

-Jim