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:
On Wed, Jul 4, 2012 at 12:46 PM, Thierry Carrez thie...@openstack.org 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
Chmouel Boudjnah wrote:
On Wed, Jul 4, 2012 at 12:46 PM, Thierry Carrez thie...@openstack.org 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
On Wed, Jul 4, 2012 at 2:46 PM, Thierry Carrez thie...@openstack.orgwrote:
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
Chmouel Boudjnah wrote:
On Wed, Jul 4, 2012 at 2:46 PM, Thierry Carrez thie...@openstack.org
mailto:thie...@openstack.org wrote:
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
Hello everyone,
Once upon a time, each OpenStack client library was independent and had
its own project in Launchpad. Then when Core projects came to rely on
them, we pulled them in as official projects but since we didn't want
to create Core projects for each of them, we considered them separate
6 matches
Mail list logo
