Dce-1.0: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
= Things to do = | = Things to do = | ||
* migrate repository from 'furbani' to 'code' | * <s>migrate repository from 'furbani' to 'code'</s> | ||
* create jenkins test suite | * create jenkins test suite | ||
* fix valgrind errors (so many) | * fix valgrind errors (so many) | ||
Revision as of 15:50, 6 March 2013
Schedule for 1.0 release
- 15th March, 2013: call for voluntary to walk through tutorial document and testing
- 30th March, 2013: new feature freeze
- (2weeks before release, TBD): code freeze
- (TBD): RC-1
- (TBD): dce-1.0 release
Call for volunteer of Testing, Reviewing
- (with Instruction)
Bugs being worked
- 1580: doxygen description Hajime
- 1594: gcov coverage test support for applications over DCE Hajime
- 1593: support DCE sub-module under myscripts directory Hajime
- 1448: DCE Kernel mode. Create a helper in order to create automatically the static routes. Hajime
- 1513: Use Linux kernel stack for ns-3 applications Hajime
- 1455: Support the python binding of DCE Hajime
Things to do
migrate repository from 'furbani' to 'code'- create jenkins test suite
- fix valgrind errors (so many)
- test with document (quick start guide, user's guide)
- update web page (http://www.nsnam.org/projects/direct-code-execution/)
- nsnam.org/doc/dce (ask Tom?)