Blueprint assignments for “trunk”
This listing shows the assignment of work for blueprints currently associated with trunk. 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 |
---|---|---|---|---|---|---|
3 Medium | Add support for installing with pip and virtualenv | 5 New | 0 Unknown | Stas Shtin | ||
1 Undefined | Extension templates | 0 Approved | 11 Implemented | Dreamtime | ||
1 Undefined | Internationalization | 0 Approved | 11 Implemented | Stas Shtin | ||
1 Undefined | Make logs more fine grained and use python's native logger | 0 Approved | 2 Deferred | |||
1 Undefined | Remove unnecessary boilerplate code, expecially w/ regards to forms | 0 Approved | 5 Started | Stas Shtin | ||
1 Undefined | Remove hardcoded urls, use reverse url resolving | 0 Approved | 11 Implemented | Stas Shtin | ||
1 Undefined | Check for valid IVR names and make sure it belongs to current account | 5 New | 0 Unknown | |||
1 Undefined | Replace current message sending with django-notices | 5 New | 0 Unknown | |||
1 Undefined | Use South for db migration / changes | 5 New | 0 Unknown | |||
1 Undefined | Add sphinx-based documentation | 5 New | 5 Started | Stas Shtin |
1 → 10 of 10 specifications | First • Previous • Next • Last |