Difference between revisions of "Ns-3.9"

From Nsnam
Jump to: navigation, search
(ns-3.9)
(update release planning)
Line 12: Line 12:
 
# August 5    -- ns-3.10 Open phase begins
 
# August 5    -- ns-3.10 Open phase begins
  
= Code under review for new feature merge =
+
= Release status =
  
We are seeking reviews for code listed in this [[Current_Development#Reviews_requested_for_ns-3_merge wiki page]].  Please help us by reviewing this code.  If you want to add more code for consideration to ns-3.9, please append your code to the bottom of the above hyperlinked wiki section.
+
== New feature merges ==
  
= Other feature requests =
+
The following seem to be on track for inclusion in ns-3.9, unless issues in the review arise.
  
* TCP NewReno
+
* MPLS
* Simple wireless models
+
* Spectrum Modeling
* Consider to merge pyviz
+
* OFDM
 +
* 802.11g patchset
 +
* Energy model
 +
* Enhancements to ns-2 trace reader (issue 473)
 +
 
 +
== Minor feature merges ==
 +
 
 +
The following minor features seem to be ready for merging:
 +
 
 +
* API for TOS bytes (issue 897)
 +
* RecvIfIndex (issue 871)
 +
 
 +
== 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. 
 +
 
 +
* Underwater Acoustic Networks (UAN):  Leonard is providing a revision next week
 +
* 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.
 +
 
 +
* 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)
 +
* app store and build system refactoring
 +
* remove ./waf --regression
 +
*

Revision as of 22:34, 21 May 2010

Main Page - Current Development - Developer FAQ - Tools - Related Projects - Project Ideas - Summer Projects

Installation - Troubleshooting - User FAQ - HOWTOs - 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

The following seem to be on track for inclusion in ns-3.9, unless issues in the review arise.

  • MPLS
  • Spectrum Modeling
  • OFDM
  • 802.11g patchset
  • Energy model
  • Enhancements to ns-2 trace reader (issue 473)

Minor feature merges

The following minor features seem to be ready for merging:

  • API for TOS bytes (issue 897)
  • RecvIfIndex (issue 871)

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.

  • Underwater Acoustic Networks (UAN): Leonard is providing a revision next week
  • 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.

  • 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)
  • app store and build system refactoring
  • remove ./waf --regression