Blueprint assignments for “0.2”
This listing shows the assignment of work for blueprints currently associated with 0.2. 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 | Fancy URL's | 0 Approved | 1 Not started | Alwin Garside | Alwin Garside | Alwin Garside |
| 4 High | Create a Front_Controller | 0 Approved | 1 Not started | Alwin Garside | Alwin Garside | Alwin Garside |
| 4 High | Prefix action methods in controllers | 0 Approved | 1 Not started | Alwin Garside | Alwin Garside | Alwin Garside |
| 4 High | Make most currently protected properties public | 0 Approved | 11 Implemented | Alwin Garside | Alwin Garside | Alwin Garside |
| 4 High | Seperate Filter, Search and Form data | 0 Approved | 5 Started | Alwin Garside | Alwin Garside | Alwin Garside |
| 4 High | Database table prefixes | 0 Approved | 1 Not started | Alwin Garside | Alwin Garside | Alwin Garside |
| 4 High | Uppercase class names | 0 Approved | 11 Implemented | Alwin Garside | Alwin Garside | Alwin Garside |
| 1 → 7 of 7 specifications | First • Previous • Next • Last |
