Blueprint assignments for “folsom”
This listing shows the assignment of work for blueprints currently associated with folsom. The drafter is responsible for getting the specification correctly written up and approved. The approver is usually the person who would sign off on the specification.
| 1 → 8 of 8 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 5 Essential | Draft Keystone V3 API blueprint | 3 Drafting | 11 Implemented | Joseph Heck | ||
| 4 High | PKI Support for Authentication and Delegation | 0 Approved | 11 Implemented | Adam Young | Adam Young | |
| 4 High | stub in initial i18n work to match other OpenStack projects | 4 Discussion | 11 Implemented | Registry Administrators | Joseph Heck | Joseph Heck |
| 3 Medium | Use '-' in all CLI option names | 0 Approved | 11 Implemented | Dean Troyer | Joseph Heck | |
| 3 Medium | Add override feature on swift middleware. | 5 New | 11 Implemented | Chmouel Boudjnah | ||
| 2 Low | Keystone should use openstack.common.importutils | 0 Approved | 11 Implemented | Zhongyue Luo | Zhongyue Luo | |
| 2 Low | Keystone should use openstack.common.jsonutils | 0 Approved | 11 Implemented | Zhongyue Luo | ||
| 2 Low | Keystone should use openstack.common.timeutils | 0 Approved | 11 Implemented | Zhongyue Luo |
| 1 → 8 of 8 specifications | First • Previous • Next • Last |
