Ns-3.9

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

1. May 3 -- ns-3.8 posted
2. May 3 -- ns-3.9 Open phase begins
3. June 16 -- Deadline for major new feature merge; begin the phase of small feature development and bug fixing
4. July 7 -- Small feature development and bug fixing ends; Maintenance phase begins
5. July 25 -- Maintenance phase ends, code freeze phase begins
6. August 5 -- ns-3.9 posted
7. August 5 -- ns-3.10 Open phase begins

Release status

New feature merges

Already merged:

• Spectrum Modeling
• 802.11g patchset

Pending merge:

• OFDM
• Energy model
• Enhancements to ns-2 trace reader (issue 473)
• Underwater Acoustic Network

To be determined:

• MPLS
• Jamming model
• NewReno TCP (issue 824)
• simple wireless models
• Rocketfuel topology reader

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)

On the fence

The following features would be nice to include in ns-3.9 but we are currently lacking any review, patch, or proposal.

• Jamming model
• fragmentation for IPv4: being worked by Vedran Miletic
• NewReno TCP (issue 824)
• simple wireless models
• NetAnim for wireless
• 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)
• ns-3 jamming 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