Blueprint assignments for “ocata”
This listing shows the assignment of work for blueprints currently associated with ocata. 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 → 7 of 7 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 4 High | Get Aodh message bus notifications | 0 Approved | 11 Implemented | dongwenjuan | dongwenjuan | |
| 4 High | A releasenotes folder must be maintained | 0 Approved | 11 Implemented | Sharat Sharma | Sharat Sharma | Ifat Afek |
| 4 High | Refactoring the format for static data source configuration | 0 Approved | 11 Implemented | Yujun Zhang | Yujun Zhang | Ifat Afek |
| 3 Medium | a datasource for collectd | 0 Approved | 11 Implemented | Eyal B | Eyal B | |
| 3 Medium | Doctor Datasource | 0 Approved | 11 Implemented | Ifat Afek | Ifat Afek | |
| 3 Medium | Support SB API defined by Doctor Inspector | 0 Approved | 11 Implemented | Ifat Afek | Ifat Afek | |
| 1 Undefined | Multi Tenancy Support | 0 Approved | 11 Implemented | Alexey Weyl | Alexey Weyl |
| 1 → 7 of 7 specifications | First • Previous • Next • Last |
