Blueprint assignments for “legacy”
This listing shows the assignment of work for blueprints currently associated with legacy. 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 → 6 of 6 specifications | First • Previous • Next • Last |
Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
---|---|---|---|---|---|---|
5 Essential | Frog Game using Pyglet instead of Pygame | 0 Approved | 6 Slow progress | Daniel Bell | Daniel Bell | Daniel Bell |
5 Essential | Porting Frog Game to Python. | 0 Approved | 11 Implemented | Daniel Bell | Daniel Bell | Daniel Bell |
5 Essential | Ability to resize game window, or have a smaller default window size. | 0 Approved | 11 Implemented | Daniel Bell | Daniel Bell | Daniel Bell |
4 High | New take on objectives. | 0 Approved | 11 Implemented | Daniel Bell | Daniel Bell | Daniel Bell |
4 High | Better graphics and images for the game. | 0 Approved | 8 Beta Available | Tim Peerdeman | Daniel Bell | Daniel Bell |
2 Low | Add ability to pause the game. | 0 Approved | 8 Beta Available | Daniel Bell | Tim Peerdeman | Daniel Bell |
1 → 6 of 6 specifications | First • Previous • Next • Last |