[openstack-dev] Duplicate code for processing REST APIs
rpodolyaka at mirantis.com
Fri Mar 14 17:09:01 UTC 2014
>>> Worth noting that there have been a few cases of projects patching OSLO bugs intheir own tree rather than fixing in OSLO then resyncing. If anybody has any tooling that can detect that, I'd love to see the results.
They shouldn't have done that :(
I totally agree, that 'syncing from incubator' strategy of reusing
common code isn't pretty, but this is what we have now. And oslo team
has been working hard to graduate libraries from incubator and then
reuse them in target projects as any other 3rd party libraries.
Hopefully, we'll no longer need to sync code from incubator soon.
On Fri, Mar 14, 2014 at 9:48 AM, Duncan Thomas <duncan.thomas at gmail.com> wrote:
> On 13 March 2014 21:13, Roman Podoliaka <rpodolyaka at mirantis.com> wrote:
>> Hi Steven,
>> Code from openstack/common/ dir is 'synced' from oslo-incubator. The
>> 'sync' is effectively a copy of oslo-incubator subtree into a project
>> source tree. As syncs are not done at the same time, the code of
>> synced modules may indeed by different for each project depending on
>> which commit of oslo-incubator was synced.
> Worth noting that there have been a few cases of projects patching
> OSLO bugs intheir own tree rather than fixing in OSLO then resyncing.
> If anybody has any tooling that can detect that, I'd love to see the
> I'm generally of the opinion that cinder is likely to be resistant to
> more parts of OSLO being used in cinder unless they are a proper
> library - syncs have caused us significant pain, code churn, review
> load and bugs in the last 12 months. I am but one voice among many,
> but I know I'm not the only member of core who feels this to be the
> case. Hopefully I can spend some time with OSLO core at the summit and
> discuss the problems I've found.
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev