Blueprints for mitaka
| 1 → 11 of 11 results | First • Previous • Next • Last |
| Priority | Blueprint | Design | Delivery | Assignee | Milestone |
|---|---|---|---|---|---|
| 5 Essential | mesos-docker-images | 0 Approved | 11 Implemented | Michal Rostecki | mitaka-2 |
| 5 Essential | neutron | 0 Approved | 11 Implemented | Michal Rostecki | mitaka-2 |
| 5 Essential | nova | 0 Approved | 11 Implemented | Angus Salkeld | mitaka-2 |
| 5 Essential | openvswitch | 0 Approved | 11 Implemented | Michal Rostecki | mitaka-2 |
| 5 Essential | vagrant | 0 Approved | 11 Implemented | Michal Rostecki | mitaka-3 |
| 4 High | multinode | 0 Approved | 7 Good progress | Michal Rostecki | mitaka-3 |
| 4 High | per-service-cli | 0 Approved | 9 Needs Code Review | Angus Salkeld | mitaka-3 |
| 3 Medium | memcached | 0 Approved | 5 Started | Proskurin Kirill | mitaka-2 |
| 3 Medium | mesos-dns | 0 Approved | 1 Not started | Artur Zarzycki | mitaka-3 |
| 3 Medium | services-use-mesos-dns | 0 Approved | 11 Implemented | Artur Zarzycki | mitaka-3 |
| 2 Low | chronos-cli | 0 Approved | 11 Implemented | Michal Rostecki | mitaka-2 |
| 1 → 11 of 11 results | First • Previous • Next • Last |
You can show declined feature goals, and if you are a driver of mitaka then you can accept goals that have been proposed.
