The cisco plugin extensions need to move to the cisco plugin directory
Bug #897817 reported by
Brad Hall
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
Medium
|
Tyler Smith | ||
Bug Description
Now that we can specify multiple extension paths these can be moved out of the main directory. It also makes more sense from a packaging perspective so that we aren't introducing cross-dependencies between common and the cisco plugin.
| Changed in quantum: | |
| milestone: | none → essex-2 |
| importance: | Undecided → Medium |
Revision history for this message
| dan wendlandt (danwent) wrote | #1 |
| Changed in quantum: | |
| milestone: | essex-2 → essex-3 |
| Changed in quantum: | |
| assignee: | nobody → Tyler Smith (tylesmit) |
| Changed in quantum: | |
| status: | New → In Progress |
| status: | In Progress → Fix Committed |
| Changed in quantum: | |
| status: | Fix Committed → Fix Released |
| Changed in quantum: | |
| milestone: | essex-3 → 2012.1 |
To post a comment you must log in.
This doesn't have an assignee. Give how close we are to the release, I think this will slide.
Can someone from the Cisco team handle this for E-3?