Blueprint assignments for “2.x”
This listing shows the assignment of work for blueprints currently associated with 2.x. 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 → 10 of 10 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 5 Essential | Secure the 2.0 release of the panel | 0 Approved | 11 Implemented | |||
| 5 Essential | Refer to users with an GUID (local part) | 0 Approved | 11 Implemented | Lars Vierbergen | ||
| 5 Essential | Refer to users with an GUID (remote part) | 0 Approved | 11 Implemented | Lars Vierbergen | ||
| 4 High | Use groups in stead of userlevel | 0 Approved | 11 Implemented | Lars Vierbergen | ||
| 4 High | New mail system | 0 Approved | 11 Implemented | Lars Vierbergen | ||
| 3 Medium | Asynchronous XHR | 0 Approved | 11 Implemented | Lars Vierbergen | ||
| 3 Medium | Use interfaces for modules that may change | 0 Approved | 11 Implemented | Lars Vierbergen | ||
| 3 Medium | Use internal errorhandling for simple requests | 0 Approved | 11 Implemented | Lars Vierbergen | ||
| 3 Medium | Use static classes in stead of one instance of the class | 0 Approved | 11 Implemented | Lars Vierbergen | ||
| 3 Medium | Split the RemoteCP Panel in 2 pieces | 0 Approved | 11 Implemented | Lars Vierbergen |
| 1 → 10 of 10 specifications | First • Previous • Next • Last |
