On Aug 28, 2014, at 7:57 AM, Thierry Carrez <thie...@openstack.org> wrote:

> Thierry Carrez wrote:
>> Doug Hellmann wrote:
>>> This makes sense to me, so let’s move ahead with your plan.
> OK, this is now done:
> Project group @ https://launchpad.net/oslo
> Oslo incubator: https://launchpad.net/oslo-incubator
> oslo.messaging: https://launchpad.net/oslo.messaging
> General blueprint view: https://blueprints.launchpad.net/oslo
> General bug view: https://bugs.launchpad.net/oslo
>>> We do have launchpad projects for some of the other oslo libraries, we just 
>>> haven’t been using them for release tracking:
>>> https://launchpad.net/python-stevedore
>>> https://launchpad.net/python-cliff
>>> https://launchpad.net/taskflow
>>> https://launchpad.net/pbr
>>> https://launchpad.net/oslo.vmware
>> Cool, good to know. I'll include them in the oslo group if we create it.
> I added pbr, but I don't have the rights to move the other ones. It
> would generally be good to have oslo-drivers added as maintainer or
> driver for those projects so that we can fix them, if they are part of oslo.

I updated the others where I have access, and contacted the owners where I 
don’t. I think only oslo.vmware and pylockfile remain to be moved.

I also created projects for the other oslo libraries and configured their bug 
and blueprints trackers.

Oslo library owners, please have someone on your team go through your bugs on 
oslo-incubator and add/move them to your library project. If the bug does not 
affect the incubator, you can retarget it by replacing the oslo-incubator 
entry, but if it does affect the incubator please just add your lib and leave 
the incubator reference there. If you don’t have permission to edit bugs in 
that way, let me know and I’ll set you up in the oslo-bugs group.


OpenStack-dev mailing list

Reply via email to