Project should use networking_hyperv namespace
Bug #1709085 reported by
Claudiu Belu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| networking-hyperv |
Fix Released
|
Low
|
Claudiu Belu | ||
Bug Description
In order to be consistent with the other networking-* projects, as well as avoiding namespace sharing with compute-hyperv, networking-hyperv should use the networking_hyperv namespace.
| Changed in networking-hyperv: | |
| importance: | Undecided → Low |
| assignee: | nobody → Claudiu Belu (cbelu) |
| Changed in networking-hyperv: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to networking-hyperv (master) | #1 |
| Changed in networking-hyperv: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/networking-hyperv 5.0.0 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 400c817c337d657
Author: Claudiu Belu <email address hidden>
Date: Mon Aug 7 13:48:46 2017 +0300
moves to networking_hyperv namespace
This project should use the networking_hyperv namespace, in order
to be consistent with the other networking-* projects, as well as
avoiding namespace sharing with compute-hyperv.
Closes-Bug: #1709085
Change-Id: Ib268aea951714e