Difference between revisions of "Network/neutron-renaming"
Markmcclain (talk | contribs) (→Code Repositories) |
Markmcclain (talk | contribs) (→Code Repositories) |
||
| Line 15: | Line 15: | ||
=== Code Repositories === | === Code Repositories === | ||
| − | python-quantumclient: | + | python-quantumclient > python-neutronclient: |
* July 2nd: Freeze python-quantumclient for prep work for client library renaming. | * July 2nd: Freeze python-quantumclient for prep work for client library renaming. | ||
| + | |||
| + | quantum > neutron: | ||
| + | * tbd | ||
Revision as of 20:49, 1 July 2013
This is our whiteboard for handling the Quantum -> Neutron transition.
Summary: Starting with the Havana release, the OpenStack Networking project's code name is Neutron. Quantum is no longer used.
Launchpad projects
Renaming projects "quantum" and "python-quantumclient":
- Rename request at: https://answers.launchpad.net/launchpad/+question/231396 (ttx): DONE
- Temporarily link Quantum repo changes to Neutron LP projects (ttx): https://review.openstack.org/34549 : DONE
- Adjust project descriptions (ttx): DONE
- Rename quantum teams in Launchpad (ttx): DONE
- Adjust releasestatus list of projects (ttx): https://review.openstack.org/34697 : DONE
- quantum-core team can't be renamed yet because they use a mailing-list: BLOCKED
Code Repositories
python-quantumclient > python-neutronclient:
- July 2nd: Freeze python-quantumclient for prep work for client library renaming.
quantum > neutron:
- tbd
