Ns-3.19

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.19. The ns-3 release process is listed here and here.

The release managers are Tom Henderson and [bpswenson3@gatech.edu Brian Swenson]. Contact them if you would like to coordinate your software inclusion with this release.

Release schedule

ns-3.19 is scheduled for December 11, 2013. There will likely be a new feature freeze about 1 month prior to that, and a code freeze about a week before the final release. More details will be posted at a later date.

Proposed supported platforms

Our primary platforms for this release are planned to be:

• Latest Fedora (32/64 bit systems)
• Ubuntu 13.10 (32/64 bit systems)
• Ubuntu 12.04 LTS and 10.04 LTS (64 bit)
• Mac OS 10.8 Mountain Lion and 10.9 Mavericks (64 bit) with Xcode 5.0
• FreeBSD 8.4, 9.2 (64 bit) using gcc and clang compilers

Packaging

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

The tarball will contain:

• pybindgen
• netanim
• ns-3.19
• bake

where bake is used to fetch optional ns-3 components.

Release goals

This release will be mainly aimed at cleaning out the tracker as much as possible. After this release, we plan to take the next step at further modularizing the code.

We aim to merge our 2013 GSoC contributions in this release.

The following goals are being worked on at this time:

• fix Python bindings generation so that it works on recent gccs (clang also?) (bug 1530)
• resolve all clang errors (bug 1560)
• Clang 3.2: https://codereview.appspot.com/10975043
• Visual Studio: https://codereview.appspot.com/8932044/

More goals to be added at a later date.

Schedule

Oct 1-15

• clang support
• look into Python bindings problem/resolution again
• clean up Roadmap and CurrentDevelopment wiki pages

Bugs being worked

We will use bugzilla to track bug priorities (esp. P1 blocker bugs) for the next release.