On Tue, Feb 18, 2014 at 9:03 PM, Joe Gordon <joe.gord...@gmail.com> wrote:
> On Wed, Feb 12, 2014 at 12:16 PM, Doug Hellmann
> <doug.hellm...@dreamhost.com> wrote:
> > If you have a change in your project that is blocked waiting for a patch
> to
> > land in oslo (in the incubator, or any of the libraries we manage)
> *please*
> > either open a blueprint or mark the associated bug as also affecting the
> > relevant oslo project, then let me know about it so I can put it on our
> > review priority list. We have a lot going on in oslo right now, but will
> do
> > our best to prioritize reviews that affect features landing in other
> > projects -- if you let us know about them.
>
>
> While I don't think this is what you meant when you said let oslo help
> you, I do have a request:
>
> While trying to do a basic oslo-incubator update ('./update.sh
> --nodeps --modules fixture --base nova --dest-dir ../nova') I hit a
> bug https://bugs.launchpad.net/oslo/+bug/1281860
>
> Due to the nature of oslo-incubator (it may break at any time) it is
> hard for downstream projects (nova, cinder etc.) to keep there
> oslo-incubator copies up to date, so when someone wants to sync across
> a new change they have to deal with many unrelated changes, some of
> which may break things. For example
>
> oslo-incubator$ ./update.sh --config-file
> ../cinder/openstack-common.conf --base cinder --dest-dir ../cinder
> cinder$ git diff --stat HEAD
> 52 files changed, 3568 insertions(+), 961 deletions(-)
>
>
> I would like to propose making the oslo team responsible for syncing
> across oslo-incubator code, they know the code base best and can fix
> things when they break. This doesn't mean no one else can use
> update.sh it just means that the oslo team would make sure that syncs
> are done in a timely fashion, so the diffs don't get too big.
>
The intent has always been for the person making a change in the incubator
to be responsible for updating consuming projects (whether that person is
an oslo core reviewer or not). That hasn't always happened -- some changes
are only synced into the project where the change was wanted, some changes
aren't synced at all.
Although it doesn't look like it from the outside, we have made significant
progress in creating the tools and processes we need to move code out of
the incubator into libraries. I expect to accelerate those moves late in
this cycle and early in the next so the libraries can be adopted early in
the next cycle.
Doug
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
