List view
Issues to be fixed in February
Due by February 28, 2013•4/4 issues closed- Due by December 31, 2012•8/8 issues closed
- Due by November 30, 2012•5/5 issues closed
- Due by October 31, 2012•5/5 issues closed
- Due by October 12, 2012•1/1 issues closed
- Due by September 30, 2012•11/11 issues closed
week 2
Due by September 17, 2012•20/20 issues closedStuff to be done by the end of the first week of competition
Due by September 9, 2012•10/10 issues closedThings that have to be ready just before the competition starts.
Due by September 3, 2012•20/20 issues closed- Due by August 24, 2012•16/16 issues closed
- Due by August 17, 2012•21/21 issues closed
- Due by August 3, 2012•43/43 issues closed
- Due by July 16, 2012•95/95 issues closed
- Due by July 17, 2012•4/4 issues closed
- Due by June 25, 2012•30/30 issues closed
- Due by June 19, 2012•41/41 issues closed
Fourth milestone.
Due by June 5, 2012•47/47 issues closedThird milestone. Due date is 5/15, but the following meeting is 5/18.
Due by May 18, 2012•15/15 issues closed- Due by May 4, 2012•15/15 issues closed
High priority items for architectural changes. 1. refactoring of underlying models. 2. support customizable widget 3. support manual meter reading
Due by March 19, 2012•11/11 issues closed- Due by April 17, 2012•22/22 issues closed
first runnable, testable, deployable release
Due by February 14, 2012•2/2 issues closed