Dce release schedule: Difference between revisions
(Created page with "This page describes the release process of ns-3-dce module.== Release Cycle == We will release newer version of dce module with the same timeframe of the ns-3 release, so that...") |
No edit summary |
||
| Line 1: | Line 1: | ||
This page describes the release process of ns-3-dce module.== Release Cycle == | This page describes the release process of ns-3-dce module. | ||
= Release Policy = | |||
== Release Decision == | |||
Each DCE release satisfies the following requirements. | |||
* Resolve all P1 bugs in [https://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=dce&list_id=3826 bugzilla (dce)] | |||
* Pass all tests by test.py | |||
* (Optional) Pass all tests with valrgrind (test.py -g) | |||
== Release Cycle == | |||
DCE will be released newer version with the same timeframe of the ns-3 release, so that users will not be confused with the version and will see the stable version/release of DCE module. | |||
== Numbering (versioning) == | |||
DCE will have its own version number, tagged at release points into ns-3-dce repository. | |||
* tag manner: dce-x.y(-RCz) | |||
== Release style == | |||
The version of DCE release is handled by using bake. | |||
== Sub-modules (quagga/umip) operations == | |||
DCE is also able to have extensions, so-called "sub-modules". The sub-modules are located under "myscripts" directory of ns-3-dce, and build all sources (i.e., models, examples, documentations, etc) with a single waf script at the top ns-3-dce directory. | |||
The design of DCE sub-modules should be aligned with the main part of ns-3, but takes this style for the moment. | |||
dce-quagga and dce-umip are the first examples of sub-modules. each module is managed and released separately. | |||
== Supported platform == | |||
Linux (distribution?) | |||
= Code = | |||
http://code.nsnam.org/ns-3-dce | |||
http://github.com/thehajime/net-next-sim | |||
= Milestone = | |||
* dce-1.0 April 2013 | |||
* dce-1.1 August 2013 | |||
* dce-1.2 December 2013 | |||
= Schedule for 1.0 release = | |||
* 1month before release: call for voluntary to walk through tutorial document and testing | |||
* ????? pickup P1 bugs | |||
* 2weeks before release: code freeze | |||
= Call for Test/Review Volunteer = | |||
(with Instruction) | |||
= 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 | |||
nsnam.org/doc/dce (Tom?) | |||
remove obsolte code/document/web from inria? | |||
= development support features = | |||
jenkins (regression/valgrind) | |||
coverage (with Linux) | |||
= development items = | |||
*DCE cradle (Bug 1499) | |||
*Elf-loader issue (Bug 1513) | |||
*mptcp | |||
*sctp | |||
*ipv6 linux stack helper | |||
*traces for arbitrary code (Bug 1598) | |||
*python binding (Bug 1455) | |||
Revision as of 15:11, 6 March 2013
This page describes the release process of ns-3-dce module.
Release Policy
Release Decision
Each DCE release satisfies the following requirements.
- Resolve all P1 bugs in bugzilla (dce)
- Pass all tests by test.py
- (Optional) Pass all tests with valrgrind (test.py -g)
Release Cycle
DCE will be released newer version with the same timeframe of the ns-3 release, so that users will not be confused with the version and will see the stable version/release of DCE module.
Numbering (versioning)
DCE will have its own version number, tagged at release points into ns-3-dce repository.
- tag manner: dce-x.y(-RCz)
Release style
The version of DCE release is handled by using bake.
Sub-modules (quagga/umip) operations
DCE is also able to have extensions, so-called "sub-modules". The sub-modules are located under "myscripts" directory of ns-3-dce, and build all sources (i.e., models, examples, documentations, etc) with a single waf script at the top ns-3-dce directory.
The design of DCE sub-modules should be aligned with the main part of ns-3, but takes this style for the moment.
dce-quagga and dce-umip are the first examples of sub-modules. each module is managed and released separately.
Supported platform
Linux (distribution?)
Code
http://code.nsnam.org/ns-3-dce http://github.com/thehajime/net-next-sim
Milestone
- dce-1.0 April 2013
- dce-1.1 August 2013
- dce-1.2 December 2013
Schedule for 1.0 release
- 1month before release: call for voluntary to walk through tutorial document and testing
- ????? pickup P1 bugs
- 2weeks before release: code freeze
Call for Test/Review Volunteer
(with Instruction)
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 nsnam.org/doc/dce (Tom?) remove obsolte code/document/web from inria?
development support features
jenkins (regression/valgrind) coverage (with Linux)
development items
- DCE cradle (Bug 1499)
- Elf-loader issue (Bug 1513)
- mptcp
- sctp
- ipv6 linux stack helper
- traces for arbitrary code (Bug 1598)
- python binding (Bug 1455)