Difference between revisions of "Ns-3.9"

From Nsnam
Jump to: navigation, search
(update release planning)
(release status-- add hyperlinks)
Line 18: Line 18:
 
The following seem to be on track for inclusion in ns-3.9, unless issues in the review arise.
 
The following seem to be on track for inclusion in ns-3.9, unless issues in the review arise.
  
* MPLS
+
* [http://codereview.appspot.com/850045/show MPLS]
* Spectrum Modeling
+
* [http://codereview.appspot.com/230045 Spectrum Modeling]
* OFDM
+
* [http://codereview.appspot.com/690041/show OFDM]
* 802.11g patchset
+
* [http://code.nsnam.org/deanarm/ns-3-dev-80211g 802.11g patchset]
* Energy model  
+
* [http://codereview.appspot.com/1008043 Energy model]
* Enhancements to ns-2 trace reader (issue 473)  
+
* [http://codereview.appspot.com/802041/show Enhancements to ns-2 trace reader (issue 473)]
  
 
== Minor feature merges ==
 
== Minor feature merges ==
Line 36: Line 36:
 
The following features would be nice to include in ns-3.9 but we are currently lacking any review, patch, or proposal.   
 
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
+
* [http://codereview.appspot.com/87043 Underwater Acoustic Networks (UAN)]:  Leonard is providing a revision next week
 
* fragmentation for IPv4:  being worked by Vedran Miletic
 
* fragmentation for IPv4:  being worked by Vedran Miletic
 
* NewReno TCP (issue 824)
 
* NewReno TCP (issue 824)
Line 56: Line 56:
 
The following features are in danger of slipping to ns-3.10 or later:
 
The following features are in danger of slipping to ns-3.10 or later:
  
* VANET mobility model (no reviews)
+
* [http://codereview.appspot.com/179068 VANET mobility model] (no reviews)
* ns-3 jamming model (no reviews)
+
* [http://codereview.appspot.com/1055041/show ns-3 jamming model] (no reviews)
 +
* [http://mailman.isi.edu/pipermail/ns-developers/2010-February/007419.html TCP Vegas] (blocked by lack of progress on TCP congestion control architecture)
 
* app store and build system refactoring
 
* app store and build system refactoring
 
* remove ./waf --regression
 
* remove ./waf --regression
 
*
 
*

Revision as of 22:40, 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.

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: