Ns-3.24

From Nsnam
Revision as of 17:37, 29 April 2015 by Tomh (talk | contribs) (move maintenance issues to 3.24)
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 release planning for ns-3.24 (August 2015). The ns-3 release process is listed here and here.

The release manager is TBD. Please contact if you would like to participate in any way in preparing the ns-3.24 release.

  • If you are interested in testing a particular feature that is planned for ns-3.24, see the section on this page for testing repos.
  • If you are interested in helping with a code review of a specific feature that you'd like to see in ns-3.24, please leave your comments on the code review pertaining to the feature of interest.
  • If you are interested to see that a specific bug be fixed, please email ns-developers mailing list, or the release manager. You will probably be asked to help with creating a patch or testing an existing patch for that bug, if so.

Release goals

1) continue the transition to a more modular build system. While a change from the Waf build system is not planned for ns-3.24, one goal is to start to allow modules outside the core of ns-3 to be maintained in separate places, and integrated using the 'bake' tool (rather than merge everything into ns-3-dev).

2) finally try to implement Object Start/Stop

3) make a major dent in the bug tracker. Can we clean out most issues on our actively maintained modules, including closing out feature requests for which we do not have anyone working on them?

4) Add new features as they become ready. In particular, finish inclusion of previous summer project code, including SOCIS 2013 and 2014 code (Bundle Protocol, TCP satellite extensions), Google Summer of Code (MLDv2, AQM queues FqCoDel and SfqCoDel), and 2014 mentored projects (Mobility Service Interface, and Python 3 support).

Release and development schedule

ns-3.24 is planned for August 2015. ns-3 makes roughly three releases per year (Dec/Jan, Apr/May, and Aug/Sept timeframes).

This means that we ought to get most new features and major changes into the simulator by late July.

More detailed scheduling is found below.

Packaging

ns-3.24 will be packaged as a source tarball as before: ns-allinone-3.24.tar.bz2.

Other details (other formats, etc.) are for further study.

A patch from ns-3.23 to ns-3.24 will also be posted.

Whether ns-3.24 is prepared in other packaging (e.g. Debian) would require a volunteer to prepare this.

Whether ns-3.24 will be distributed also as a Docker container would require a volunteer to prepare this.

Release platforms

We usually try to keep pace with the latest popular versions of Linux, OS X, and FreeBSD. For the ns-3.24 release, we plan to support the following systems and compilers:

TBD

Testing repos

Some repositories, based on a recent copy of ns-3-dev, will be available for testing specific features.

TBD

New features

Developers are working or planning to work on the following new features for ns-3.24.

Note: there is no guarantee that the features will be finished by the end of the release cycle, so check back for progress/status.

Energy Enhancements (Cristiano Tapparello)

Cristiano plans several additions:

  • New models for energy sources, converters, predictors, and sensor models (code to be posted soon)
  • LithiumIonEnergySource helper
  • RVBatteryModel bug fixes

DSR

Status: Tomasz is working on addressing the review comments (no update recently)

Epidemic Routing

Status: Still undergoing code review revisions.

UAN WOSS

Satellite models

Statistics

Enhancements to data collection framework are planned to enable more flexible configuration of time series, time avearge, and asynchronous event plotting (Li Li, Felipe Perrone, Tom Henderson).

TCP

  • RttEstimator improvements (Natale Patriciello)
    • Resolve bug 1412 RttEstimator to network module


Software maintenance issues

Status: No change on the above lately.