openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #14166
Re: Bugs for Client libraries back to their own projects
-
To:
openstack@xxxxxxxxxxxxxxxxxxx
-
From:
Thierry Carrez <thierry@xxxxxxxxxxxxx>
-
Date:
Wed, 04 Jul 2012 14:46:33 +0200
-
Cc:
Chmouel Boudjnah <chmouel@xxxxxxxxxxx>
-
In-reply-to:
<CAPeWyqzME8henaoiQOa6zG415UoNo+K9UbgVNEzQ_+L=8AeA8g@mail.gmail.com>
-
Organization:
OpenStack
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
Chmouel Boudjnah wrote:
> On Wed, Jul 4, 2012 at 12:46 PM, Thierry Carrez <thierry@xxxxxxxxxxxxx> wrote:
>> Thierry Carrez wrote:
>>> So unless someone explains why we shouldn't do it, next week I'll start
>>> the process of migrating back all bugs tagged "python-*client" from
>>> their "parent" project to their own project.
>> Bugs for client libraries are now available at:
>
> Any chances to move the blueprints as well?
Blueprints can (and should) be moved as well.. but there is no way to do
automatically identify the blueprints that are pure client stuff, so it
will be manual:
When you're on a blueprint you want to move, click "Re-target blueprint"
on the top right and select the python-PROJECTclient project.
Regards,
--
Thierry Carrez (ttx)
Release Manager, OpenStack
Follow ups
References