[Ns-developers] ns-3.1 roadmap

[Tom Henderson]

I would like to start some discussion on what is included in our ns-3.1 release, and then we can set a schedule for dealing with the remaining issues.

Later, I would like to post the results of this thread, and maintain our development status, on the wiki.

I had previously announced the following ns-3.1 release plan:
- ns-3.1-beta when Python bindings are done (early May?)
- ns-3.1 release on June 15

Major software issues
=====================

0) finish the Python bindings of the existing API

1) how to make it easy for users to write their own Python bindings for C++ extensions that they implement

2) finalize ns log issues (existing mailing list thread)

3) finalize ns socket issues (existing thread)
 - merge ns-3-simu?

4) resolve trace path issues (existing thread)

5) finalize helper APIs

6) PointToPoint and CSMA net device cleanup

7) merge ns-3-doc?

8) move Doxygen to .cc files?

Minor software issues
=====================

- resolve most of existing logged bugs
  -- we should identify any that are post-3.1 release, or in WONTFIX state for the moment

-  other items to clean up that are not logged anywhere?

Documentation
==============

1) a better definition of what models are supposed to be doing
   -- e.g., along the lines of Mathieu's "wifi.h" Doxygen

2) write or revise the following tutorial chapters
- using Random Variables and setting seeds
- Packets and Socket API
- Using the Attribute system (revise)
- Topology and Helper APIs
- how to use the logging system
- how to use the tracing system

3) source code comments, Doxygen, more example scripts (too many little items to list here, for now, but we need to delegate some cleanup)

Administrative
==============

- decide on release platforms and supported configurations
- packaging (e.g. rpms) and distribution
- ns-3.1 or ns-3.1.0 (i.e., institute major/minor numbering, or keep with ns-2 style?)
- create ns-3-users mailing list