Difference between revisions of "Network/neutron-renaming"
(→Launchpad projects) |
(→Launchpad projects) |
||
Line 3: | Line 3: | ||
=== Launchpad projects === | === Launchpad projects === | ||
Renaming projects "quantum" and "python-quantumclient": | Renaming projects "quantum" and "python-quantumclient": | ||
− | * Rename request pending at: https://answers.launchpad.net/launchpad/+question/231396 | + | * Rename request pending at: https://answers.launchpad.net/launchpad/+question/231396 (ttx) |
− | * Once done, https://review.openstack.org/34549 should be accepted so that quantum changes are linked to Neutron bugs, until the repositories are transitioned too | + | * Once done, https://review.openstack.org/34549 should be accepted so that quantum changes are linked to Neutron bugs, until the repositories are transitioned too (ttx) |
+ | * Adjust project descriptions (ttx) | ||
+ | * Rename all *quantum teams in Launchpad (ttx) | ||
=== Code Repositories === | === Code Repositories === | ||
tbd | tbd |
Revision as of 13:43, 26 June 2013
This is our whiteboard for handling the Quantum -> Neutron transition.
Launchpad projects
Renaming projects "quantum" and "python-quantumclient":
- Rename request pending at: https://answers.launchpad.net/launchpad/+question/231396 (ttx)
- Once done, https://review.openstack.org/34549 should be accepted so that quantum changes are linked to Neutron bugs, until the repositories are transitioned too (ttx)
- Adjust project descriptions (ttx)
- Rename all *quantum teams in Launchpad (ttx)
Code Repositories
tbd