Ns-3.9
Jump to navigation
Jump to search
Main Page - Roadmap - Summer Projects - Project Ideas - Developer FAQ - Tools - Related Projects
HOWTOs - Installation - Troubleshooting - User FAQ - Samples - Models - Education - Contributed Code - Papers
This page summarizes the ongoing release planning for ns-3.9. We are seeking a volunteer for release manager for the final release stages. Josh Pelkey and Tom Henderson are acting release managers at this time.
Tentative Release Schedule
May 3 -- ns-3.8 postedMay 3 -- ns-3.9 Open phase begins- June 16 --
Deadline for proposing major new features to be merged;begin the phase of small feature development and bug fixing - June 25 -- Deadline for merge of major features identified on the release page
- July 7 -- Small feature development and bug fixing ends; Maintenance phase begins
- July 25 -- Maintenance phase ends, code freeze phase begins
- August 5 -- ns-3.9 posted
- August 5 -- ns-3.10 Open phase begins
Release status
New feature merges
Already merged:
- Spectrum Modeling
- OFDM
- Bring rate representation in line with IEEE standard
- Enhancements to ns-2 trace reader (issue 473)
Pending merge:
- Energy model
- Underwater Acoustic Network
- 802.11g and related items
- Rocketfuel topology reader
Will decide next week, based on review:
Likely for ns-3.10:
Minor feature merges
The following minor features seem to be ready for merging or should be fixable soon:
- API for TOS bytes (issue 897) may wait for netfilter support
- RecvIfIndex (issue 671)
- NetAnim trace hooks for wireless (patch in preparation)
- Generic sequence number class (issue 385)
- Class name rename Scalar->Dimensionless (issue 445)
Critical issues
These issues are candidates to become blocker issues.
- Doxygen incomplete (discussed on list already)
- peekData warnings (issues 846 and 912)
- AODV problems reported by Kevin Peters (also, issue 879)
- Wimax serialize (issue 905)
Features that may slip
The following features are in danger of slipping to ns-3.10 or later:
- VANET mobility model (no reviews)
- TCP Vegas (blocked by lack of progress on TCP congestion control architecture)
- Chord/DHT (authors are planning to revise code based on comments)
- app store and build system refactoring
- remove ./waf --regression