Ns-3.18: Difference between revisions

From Nsnam
Jump to navigation Jump to search
No edit summary
Line 8: Line 8:


ns-3.18 was scheduled for August 14, 2013 and then slipped to August 21, 2013.  The release has been rescheduled for Thursday August 29.
ns-3.18 was scheduled for August 14, 2013 and then slipped to August 21, 2013.  The release has been rescheduled for Thursday August 29.
* '''Release candidate:'''  Please test our ns-3.18 [http://www.nsnam.org/release/ns-allinone-3.18.rc1.tar.bz2 release candidate]
* '''Release candidate 2 (August 27):'''  Please test our ns-3.18 [http://www.nsnam.org/release/ns-allinone-3.18.rc2.tar.bz2 release candidate]


= Proposed supported platforms =
= Proposed supported platforms =

Revision as of 04:15, 28 August 2013

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

The release manager is Tom Henderson.

Release schedule

ns-3.18 was scheduled for August 14, 2013 and then slipped to August 21, 2013. The release has been rescheduled for Thursday August 29.

Proposed supported platforms

Our primary platforms for this release are planned to be:

  • Fedora 18 and 19 (32/64 bit systems)
  • Ubuntu 13.04 (32/64 bit systems)
  • Ubuntu 12.04 LTS and 10.04 LTS (64 bit)
  • Mac OS 10.8 (64 bit)
  • FreeBSD 8.4, 9.1 (64 bit) using gcc compiler

The following also are planned to be lightly tested:

  • Cygwin 1.7.20.1 (for Windows 7)
  • Mac OS X 10.7 (64 bit)
  • Linux Mint 15
  • CentOS

Packaging

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

The tarball will contain:

  • pybindgen
  • netanim
  • ns-3.18
  • bake

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

feature goals

These features are presently being worked on and reviewed:

Cleanup

Note (Aug 18): additional cleanup (including clang and visual studio) will likely slip until the next release cycle

We need to take a pass through the code base to remove deprecated code.

Cleanup code to silence compiler warnings and solve other compiler issues:

We need to clean up the "Current Development" and "Roadmap" pages to make it clear who is doing what:

1) make clear entry point to 'Current work' from main web page

2) consider to merge 'Current development' and 'Roadmap' pages, and make sure that a person is associated with each feature that is being actively worked.

3) tie this into our "release page" for each release, so people can understand whether any given issue on the front burner or not

4) make updating this a job of the release manager

additional issues

Here are some additional issues that need to be discussed and worked on (but will slip to ns-3.19 or later since no patches were proposed):

  • bug 1605 is a longstanding issue about jitter in our models
  • bug 1561 modular doxygen
  • bug 1347 modular headers
  • bug 1334 long-term support for ns-3 releases
  • bug 1327 packaging

additional new feature reviews

The following code will probably slip beyond ns-3.18, due to lack of recent activity:

Bugs being worked

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

Bugs to close

Bugs will be closed on best effort basis.