Nsnam - User contributions [en]

Ns-3.7

2010-01-28T12:15:46Z

Fmoatamr: /* Wimax applications */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# <s>October 21 -- ns-3.7 '''''Open phase begins''''';</s>
# <s>November 18 -- Deadline for new feature merge;</s>
# <s>November 18 -- Begin the phase of small feature development and bug fixing;</s>
# <s>December 16 -- Small feature development and bug fixing ends;</s>
# <s>December 16 -- '''''Open phase ends''''';</s>
# <s>December 16 -- '''''Maintenance phase begins''''';></s>
# <s>January 6 -- '''''Maintenance phase ends''''';</s>
# <s>January 6 -- '''''Code freeze phase begins''''';</s>
# <s>January 6 -- ns-3.7-RC1;</s>
# <s>January 8 -- ns-3.7-RC2;</s>
# <s>January 12 -- ns-3.7-RC3;</s>
# <s>January 22 -- ns-3.7-RC4;</s>
# <s>January 27 -- ns-3.7 posted;</s>
# <s>January 27 -- '''''Code freeze phase ends''''';</s>
# January 27 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

No more candidates because ns-3.7 is released.

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev
* ''Features'':
** Adds WIFI_PHY_STANDARD_80211p_CCH, 802.11p Control Channel specifications, as an enumerated case of WifiPhyStandard
** Adds WIFI_PHY_STANDARD_80211p_SCH, 802.11p Service Channel specifications, as an enumerated case of WifiPhyStandard
** The above standards are available to the qadhoc-wifi-mac, qap-wifi-mac, and qsta-wifi-mac models.
** PHY, MAC and DCF parameters are set according to IEEE Trial-Use Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-channel Operation, IEEE Std 1609.4-2006
** Code is based on the existing WIFI_PHY_STANDARD_80211_10Mhz WifiPhyStandard

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html
* ''Features'':
** Provides an inteface to NetAnim, a network animator for point-to-point links in ns-3. The interface generates a custom trace file for use with the NetAnim program
** New topology helpers have been introduced including PointToPointStarHelper, PointToPointDumbbellHelper, PointToPointGridHelper, and CsmaStarHelper. These topology helpers provide a simply way to setup common topologies, and the BoundingBox method within each helper allows easy placement of nodes on the NetAnim canvas
** Example scripts are located in examples/animation for examples on using the animation interface
** Future: Support other link types besides point-to-point. For wireless links, this requires an update to the (completely separate) NetAnim program in order to handle wireless devices

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

=== Wimax applications ===

* ''Review location'':
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merge

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2010-01-28T12:15:23Z

Fmoatamr: /* Candidate Contributions for Inclusion in ns-3.7 */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# <s>October 21 -- ns-3.7 '''''Open phase begins''''';</s>
# <s>November 18 -- Deadline for new feature merge;</s>
# <s>November 18 -- Begin the phase of small feature development and bug fixing;</s>
# <s>December 16 -- Small feature development and bug fixing ends;</s>
# <s>December 16 -- '''''Open phase ends''''';</s>
# <s>December 16 -- '''''Maintenance phase begins''''';></s>
# <s>January 6 -- '''''Maintenance phase ends''''';</s>
# <s>January 6 -- '''''Code freeze phase begins''''';</s>
# <s>January 6 -- ns-3.7-RC1;</s>
# <s>January 8 -- ns-3.7-RC2;</s>
# <s>January 12 -- ns-3.7-RC3;</s>
# <s>January 22 -- ns-3.7-RC4;</s>
# <s>January 27 -- ns-3.7 posted;</s>
# <s>January 27 -- '''''Code freeze phase ends''''';</s>
# January 27 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

No more candidates because ns-3.7 is released.

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev
* ''Features'':
** Adds WIFI_PHY_STANDARD_80211p_CCH, 802.11p Control Channel specifications, as an enumerated case of WifiPhyStandard
** Adds WIFI_PHY_STANDARD_80211p_SCH, 802.11p Service Channel specifications, as an enumerated case of WifiPhyStandard
** The above standards are available to the qadhoc-wifi-mac, qap-wifi-mac, and qsta-wifi-mac models.
** PHY, MAC and DCF parameters are set according to IEEE Trial-Use Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-channel Operation, IEEE Std 1609.4-2006
** Code is based on the existing WIFI_PHY_STANDARD_80211_10Mhz WifiPhyStandard

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html
* ''Features'':
** Provides an inteface to NetAnim, a network animator for point-to-point links in ns-3. The interface generates a custom trace file for use with the NetAnim program
** New topology helpers have been introduced including PointToPointStarHelper, PointToPointDumbbellHelper, PointToPointGridHelper, and CsmaStarHelper. These topology helpers provide a simply way to setup common topologies, and the BoundingBox method within each helper allows easy placement of nodes on the NetAnim canvas
** Example scripts are located in examples/animation for examples on using the animation interface
** Future: Support other link types besides point-to-point. For wireless links, this requires an update to the (completely separate) NetAnim program in order to handle wireless devices

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

=== Wimax applications ===

* ''Review location'':
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2010-01-27T13:40:26Z

Fmoatamr: /* Tentative ns-3.7 Release Schedule */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# <s>October 21 -- ns-3.7 '''''Open phase begins''''';</s>
# <s>November 18 -- Deadline for new feature merge;</s>
# <s>November 18 -- Begin the phase of small feature development and bug fixing;</s>
# <s>December 16 -- Small feature development and bug fixing ends;</s>
# <s>December 16 -- '''''Open phase ends''''';</s>
# <s>December 16 -- '''''Maintenance phase begins''''';></s>
# <s>January 6 -- '''''Maintenance phase ends''''';</s>
# <s>January 6 -- '''''Code freeze phase begins''''';</s>
# <s>January 6 -- ns-3.7-RC1;</s>
# <s>January 8 -- ns-3.7-RC2;</s>
# <s>January 12 -- ns-3.7-RC3;</s>
# <s>January 22 -- ns-3.7-RC4;</s>
# <s>January 27 -- ns-3.7 posted;</s>
# <s>January 27 -- '''''Code freeze phase ends''''';</s>
# January 27 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': will be merged at the starting of ns-3.8
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev
* ''Features'':
** Adds WIFI_PHY_STANDARD_80211p_CCH, 802.11p Control Channel specifications, as an enumerated case of WifiPhyStandard
** Adds WIFI_PHY_STANDARD_80211p_SCH, 802.11p Service Channel specifications, as an enumerated case of WifiPhyStandard
** The above standards are available to the qadhoc-wifi-mac, qap-wifi-mac, and qsta-wifi-mac models.
** PHY, MAC and DCF parameters are set according to IEEE Trial-Use Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-channel Operation, IEEE Std 1609.4-2006
** Code is based on the existing WIFI_PHY_STANDARD_80211_10Mhz WifiPhyStandard

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html
* ''Features'':
** Provides an inteface to NetAnim, a network animator for point-to-point links in ns-3. The interface generates a custom trace file for use with the NetAnim program
** New topology helpers have been introduced including PointToPointStarHelper, PointToPointDumbbellHelper, PointToPointGridHelper, and CsmaStarHelper. These topology helpers provide a simply way to setup common topologies, and the BoundingBox method within each helper allows easy placement of nodes on the NetAnim canvas
** Example scripts are located in examples/animation for examples on using the animation interface
** Future: Support other link types besides point-to-point. For wireless links, this requires an update to the (completely separate) NetAnim program in order to handle wireless devices

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

=== Wimax applications ===

* ''Review location'':
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2010-01-22T16:12:13Z

Fmoatamr: /* Tentative ns-3.7 Release Schedule */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# <s>October 21 -- ns-3.7 '''''Open phase begins''''';</s>
# <s>November 18 -- Deadline for new feature merge;</s>
# <s>November 18 -- Begin the phase of small feature development and bug fixing;</s>
# <s>December 16 -- Small feature development and bug fixing ends;</s>
# <s>December 16 -- '''''Open phase ends''''';</s>
# <s>December 16 -- '''''Maintenance phase begins''''';></s>
# <s>January 6 -- '''''Maintenance phase ends''''';</s>
# <s>January 6 -- '''''Code freeze phase begins''''';</s>
# <s>January 6 -- ns-3.7-RC1;</s>
# <s>January 8 -- ns-3.7-RC2;</s>
# <s>January 12 -- ns-3.7-RC3;</s>
# <s>January 22 -- ns-3.7-RC4;</s>
# January 27 -- ns-3.7 posted;
# January 27 -- '''''Code freeze phase ends''''';
# January 27 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': will be merged at the starting of ns-3.8
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev
* ''Features'':
** Adds WIFI_PHY_STANDARD_80211p_CCH, 802.11p Control Channel specifications, as an enumerated case of WifiPhyStandard
** Adds WIFI_PHY_STANDARD_80211p_SCH, 802.11p Service Channel specifications, as an enumerated case of WifiPhyStandard
** The above standards are available to the qadhoc-wifi-mac, qap-wifi-mac, and qsta-wifi-mac models.
** PHY, MAC and DCF parameters are set according to IEEE Trial-Use Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-channel Operation, IEEE Std 1609.4-2006
** Code is based on the existing WIFI_PHY_STANDARD_80211_10Mhz WifiPhyStandard

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html
* ''Features'':
** Provides an inteface to NetAnim, a network animator for point-to-point links in ns-3. The interface generates a custom trace file for use with the NetAnim program
** New topology helpers have been introduced including PointToPointStarHelper, PointToPointDumbbellHelper, PointToPointGridHelper, and CsmaStarHelper. These topology helpers provide a simply way to setup common topologies, and the BoundingBox method within each helper allows easy placement of nodes on the NetAnim canvas
** Example scripts are located in examples/animation for examples on using the animation interface
** Future: Support other link types besides point-to-point. For wireless links, this requires an update to the (completely separate) NetAnim program in order to handle wireless devices

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

=== Wimax applications ===

* ''Review location'':
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2010-01-15T17:25:27Z

Fmoatamr: /* Tentative ns-3.7 Release Schedule */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# <s>October 21 -- ns-3.7 '''''Open phase begins''''';</s>
# <s>November 18 -- Deadline for new feature merge;</s>
# <s>November 18 -- Begin the phase of small feature development and bug fixing;</s>
# <s>December 16 -- Small feature development and bug fixing ends;</s>
# <s>December 16 -- '''''Open phase ends''''';</s>
# <s>December 16 -- '''''Maintenance phase begins''''';></s>
# <s>January 6 -- '''''Maintenance phase ends''''';</s>
# <s>January 6 -- '''''Code freeze phase begins''''';</s>
# <s>January 6 -- ns-3.7-RC1;</s>
# <s>January 8 -- ns-3.7-RC2;</s>
# <s>January 12 -- ns-3.7-RC3;</s>
# January 22 -- ns-3.7-RC4;
# January 27 -- ns-3.7 posted;
# January 27 -- '''''Code freeze phase ends''''';
# January 27 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': will be merged at the starting of ns-3.8
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev
* ''Features'':
** Adds WIFI_PHY_STANDARD_80211p_CCH, 802.11p Control Channel specifications, as an enumerated case of WifiPhyStandard
** Adds WIFI_PHY_STANDARD_80211p_SCH, 802.11p Service Channel specifications, as an enumerated case of WifiPhyStandard
** The above standards are available to the qadhoc-wifi-mac, qap-wifi-mac, and qsta-wifi-mac models.
** PHY, MAC and DCF parameters are set according to IEEE Trial-Use Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-channel Operation, IEEE Std 1609.4-2006
** Code is based on the existing WIFI_PHY_STANDARD_80211_10Mhz WifiPhyStandard

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html
* ''Features'':
** Provides an inteface to NetAnim, a network animator for point-to-point links in ns-3. The interface generates a custom trace file for use with the NetAnim program
** New topology helpers have been introduced including PointToPointStarHelper, PointToPointDumbbellHelper, PointToPointGridHelper, and CsmaStarHelper. These topology helpers provide a simply way to setup common topologies, and the BoundingBox method within each helper allows easy placement of nodes on the NetAnim canvas
** Example scripts are located in examples/animation for examples on using the animation interface
** Future: Support other link types besides point-to-point. For wireless links, this requires an update to the (completely separate) NetAnim program in order to handle wireless devices

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

=== Wimax applications ===

* ''Review location'':
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2010-01-14T11:01:17Z

Fmoatamr: /* Tentative ns-3.7 Release Schedule */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# <s>October 21 -- ns-3.7 '''''Open phase begins''''';</s>
# <s>November 18 -- Deadline for new feature merge;</s>
# <s>November 18 -- Begin the phase of small feature development and bug fixing;</s>
# <s>December 16 -- Small feature development and bug fixing ends;</s>
# <s>December 16 -- '''''Open phase ends''''';</s>
# <s>December 16 -- '''''Maintenance phase begins''''';></s>
# <s>January 6 -- '''''Maintenance phase ends''''';</s>
# <s>January 6 -- '''''Code freeze phase begins''''';</s>
# <s>January 6 -- ns-3.7-RC1;</s>
# <s>January 8 -- ns-3.7-RC2;</s>
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': will be merged at the starting of ns-3.8
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev
* ''Features'':
** Adds WIFI_PHY_STANDARD_80211p_CCH, 802.11p Control Channel specifications, as an enumerated case of WifiPhyStandard
** Adds WIFI_PHY_STANDARD_80211p_SCH, 802.11p Service Channel specifications, as an enumerated case of WifiPhyStandard
** The above standards are available to the qadhoc-wifi-mac, qap-wifi-mac, and qsta-wifi-mac models.
** PHY, MAC and DCF parameters are set according to IEEE Trial-Use Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-channel Operation, IEEE Std 1609.4-2006
** Code is based on the existing WIFI_PHY_STANDARD_80211_10Mhz WifiPhyStandard

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html
* ''Features'':
** Provides an inteface to NetAnim, a network animator for point-to-point links in ns-3. The interface generates a custom trace file for use with the NetAnim program
** New topology helpers have been introduced including PointToPointStarHelper, PointToPointDumbbellHelper, PointToPointGridHelper, and CsmaStarHelper. These topology helpers provide a simply way to setup common topologies, and the BoundingBox method within each helper allows easy placement of nodes on the NetAnim canvas
** Example scripts are located in examples/animation for examples on using the animation interface
** Future: Support other link types besides point-to-point. For wireless links, this requires an update to the (completely separate) NetAnim program in order to handle wireless devices

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

=== Wimax applications ===

* ''Review location'':
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2010-01-10T16:09:22Z

Fmoatamr: /* Tentative ns-3.7 Release Schedule */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# <s>October 21 -- ns-3.7 '''''Open phase begins''''';</s>
# <s>November 18 -- Deadline for new feature merge;</s>
# <s>November 18 -- Begin the phase of small feature development and bug fixing;</s>
# <s>December 16 -- Small feature development and bug fixing ends;</s>
# <s>December 16 -- '''''Open phase ends''''';</s>
# <s>December 16 -- '''''Maintenance phase begins''''';></s>
# <s>January 6 -- '''''Maintenance phase ends''''';</s>
# <s>January 6 -- '''''Code freeze phase begins''''';</s>
# <s>January 6 -- ns-3.7-RC1;</s>
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': will be merged at the starting of ns-3.8
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev
* ''Features'':
** Adds WIFI_PHY_STANDARD_80211p_CCH, 802.11p Control Channel specifications, as an enumerated case of WifiPhyStandard
** Adds WIFI_PHY_STANDARD_80211p_SCH, 802.11p Service Channel specifications, as an enumerated case of WifiPhyStandard
** The above standards are available to the qadhoc-wifi-mac, qap-wifi-mac, and qsta-wifi-mac models.
** PHY, MAC and DCF parameters are set according to IEEE Trial-Use Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-channel Operation, IEEE Std 1609.4-2006
** Code is based on the existing WIFI_PHY_STANDARD_80211_10Mhz WifiPhyStandard

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html
* ''Features'':
** Provides an inteface to NetAnim, a network animator for point-to-point links in ns-3. The interface generates a custom trace file for use with the NetAnim program
** New topology helpers have been introduced including PointToPointStarHelper, PointToPointDumbbellHelper, PointToPointGridHelper, and CsmaStarHelper. These topology helpers provide a simply way to setup common topologies, and the BoundingBox method within each helper allows easy placement of nodes on the NetAnim canvas
** Example scripts are located in examples/animation for examples on using the animation interface
** Future: Support other link types besides point-to-point. For wireless links, this requires an update to the (completely separate) NetAnim program in order to handle wireless devices

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

=== Wimax applications ===

* ''Review location'':
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2010-01-07T13:03:39Z

Fmoatamr: /* Tentative ns-3.7 Release Schedule */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# <s>October 21 -- ns-3.7 '''''Open phase begins''''';</s>
# <s>November 18 -- Deadline for new feature merge;</s>
# <s>November 18 -- Begin the phase of small feature development and bug fixing;</s>
# <s>December 16 -- Small feature development and bug fixing ends;</s>
# <s>December 16 -- '''''Open phase ends''''';</s>
# <s>December 16 -- '''''Maintenance phase begins''''';></s>
# <s>January 6 -- '''''Maintenance phase ends''''';</s>
# <s>January 6 -- '''''Code freeze phase begins''''';</s>
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': will be merged at the starting of ns-3.8
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev
* ''Features'':
** Adds WIFI_PHY_STANDARD_80211p_CCH, 802.11p Control Channel specifications, as an enumerated case of WifiPhyStandard
** Adds WIFI_PHY_STANDARD_80211p_SCH, 802.11p Service Channel specifications, as an enumerated case of WifiPhyStandard
** The above standards are available to the qadhoc-wifi-mac, qap-wifi-mac, and qsta-wifi-mac models.
** PHY, MAC and DCF parameters are set according to IEEE Trial-Use Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-channel Operation, IEEE Std 1609.4-2006
** Code is based on the existing WIFI_PHY_STANDARD_80211_10Mhz WifiPhyStandard

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html
* ''Features'':
** Provides an inteface to NetAnim, a network animator for point-to-point links in ns-3. The interface generates a custom trace file for use with the NetAnim program
** New topology helpers have been introduced including PointToPointStarHelper, PointToPointDumbbellHelper, PointToPointGridHelper, and CsmaStarHelper. These topology helpers provide a simply way to setup common topologies, and the BoundingBox method within each helper allows easy placement of nodes on the NetAnim canvas
** Example scripts are located in examples/animation for examples on using the animation interface
** Future: Support other link types besides point-to-point. For wireless links, this requires an update to the (completely separate) NetAnim program in order to handle wireless devices

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

=== Wimax applications ===

* ''Review location'':
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2010-01-06T17:26:27Z

Fmoatamr: /* Tentative ns-3.7 Release Schedule */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# <s>October 21 -- ns-3.7 '''''Open phase begins''''';</s>
# <s>November 18 -- Deadline for new feature merge;</s>
# <s>November 18 -- Begin the phase of small feature development and bug fixing;</s>
# <s>December 16 -- Small feature development and bug fixing ends;</s>
# <s>December 16 -- '''''Open phase ends''''';</s>
# <s>December 16 -- '''''Maintenance phase begins''''';></s>
# <s>January 6 -- '''''Maintenance phase ends''''';</s>
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': will be merged at the starting of ns-3.8
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev
* ''Features'':
** Adds WIFI_PHY_STANDARD_80211p_CCH, 802.11p Control Channel specifications, as an enumerated case of WifiPhyStandard
** Adds WIFI_PHY_STANDARD_80211p_SCH, 802.11p Service Channel specifications, as an enumerated case of WifiPhyStandard
** The above standards are available to the qadhoc-wifi-mac, qap-wifi-mac, and qsta-wifi-mac models.
** PHY, MAC and DCF parameters are set according to IEEE Trial-Use Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-channel Operation, IEEE Std 1609.4-2006
** Code is based on the existing WIFI_PHY_STANDARD_80211_10Mhz WifiPhyStandard

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html
* ''Features'':
** Provides an inteface to NetAnim, a network animator for point-to-point links in ns-3. The interface generates a custom trace file for use with the NetAnim program
** New topology helpers have been introduced including PointToPointStarHelper, PointToPointDumbbellHelper, PointToPointGridHelper, and CsmaStarHelper. These topology helpers provide a simply way to setup common topologies, and the BoundingBox method within each helper allows easy placement of nodes on the NetAnim canvas
** Example scripts are located in examples/animation for examples on using the animation interface
** Future: Support other link types besides point-to-point. For wireless links, this requires an update to the (completely separate) NetAnim program in order to handle wireless devices

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

=== Wimax applications ===

* ''Review location'':
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2009-12-07T08:17:56Z

Fmoatamr: /* 802.11p WiFi standards */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': will be merged at the starting of ns-3.8
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev
* ''Features'':
** Adds WIFI_PHY_STANDARD_80211p_CCH, 802.11p Control Channel specifications, as an enumerated case of WifiPhyStandard
** Adds WIFI_PHY_STANDARD_80211p_SCH, 802.11p Service Channel specifications, as an enumerated case of WifiPhyStandard
** The above standards are available to the qadhoc-wifi-mac, qap-wifi-mac, and qsta-wifi-mac models.
** PHY, MAC and DCF parameters are set according to IEEE Trial-Use Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-channel Operation, IEEE Std 1609.4-2006
** Code is based on the existing WIFI_PHY_STANDARD_80211_10Mhz WifiPhyStandard

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html
* ''Features'':
** Provides an inteface to NetAnim, a network animator for point-to-point links in ns-3. The interface generates a custom trace file for use with the NetAnim program
** New topology helpers have been introduced including PointToPointStarHelper, PointToPointDumbbellHelper, PointToPointGridHelper, and CsmaStarHelper. These topology helpers provide a simply way to setup common topologies, and the BoundingBox method within each helper allows easy placement of nodes on the NetAnim canvas
** Example scripts are located in examples/animation for examples on using the animation interface
** Future: Support other link types besides point-to-point. For wireless links, this requires an update to the (completely separate) NetAnim program in order to handle wireless devices

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

=== Wimax applications ===

* ''Review location'':
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2009-12-07T08:17:11Z

Fmoatamr: /* ns-3.7 Features Merged */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': will be merged at the starting of ns-3.8
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev
* ''Features'':
** Adds WIFI_PHY_STANDARD_80211p_CCH, 802.11p Control Channel specifications, as an enumerated case of WifiPhyStandard
** Adds WIFI_PHY_STANDARD_80211p_SCH, 802.11p Service Channel specifications, as an enumerated case of WifiPhyStandard
** The above standards are available to the qadhoc-wifi-mac, qap-wifi-mac, and qsta-wifi-mac models.
** PHY,MAC, and DCF parameters are set according to IEEE Trial-Use Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-channel Operation, IEEE Std 1609.4-2006
** Code is based on the existing WIFI_PHY_STANDARD_80211_10Mhz WifiPhyStandard

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html
* ''Features'':
** Provides an inteface to NetAnim, a network animator for point-to-point links in ns-3. The interface generates a custom trace file for use with the NetAnim program
** New topology helpers have been introduced including PointToPointStarHelper, PointToPointDumbbellHelper, PointToPointGridHelper, and CsmaStarHelper. These topology helpers provide a simply way to setup common topologies, and the BoundingBox method within each helper allows easy placement of nodes on the NetAnim canvas
** Example scripts are located in examples/animation for examples on using the animation interface
** Future: Support other link types besides point-to-point. For wireless links, this requires an update to the (completely separate) NetAnim program in order to handle wireless devices

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

=== Wimax applications ===

* ''Review location'':
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2009-12-04T16:59:23Z

Fmoatamr: /* ns-3.7 Features Merged */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': will be merged at the starting of ns-3.8
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html
* ''Features'':
** Provides an inteface to NetAnim, a network animator for point-to-point links in ns-3. The interface generates a custom trace file for use with the NetAnim program
** New topology helpers have been introduced including PointToPointStarHelper, PointToPointDumbbellHelper, PointToPointGridHelper, and CsmaStarHelper. These topology helpers provide a simply way to setup common topologies, and the BoundingBox method within each helper allows easy placement of nodes on the NetAnim canvas
** Example scripts are located in examples/animation for examples on using the animation interface
** Future: Support other link types besides point-to-point. For wireless links, this requires an update to the (completely separate) NetAnim program in order to handle wireless devices

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

=== Wimax applications ===

* ''Review location'':
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2009-12-04T09:29:11Z

Fmoatamr: /* IPv6 Extension and Option Headers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': will be merged at the starting of ns-3.8
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Merged

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2009-12-02T16:42:54Z

Fmoatamr: /* WiMAX */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': will be merged at the starting of ns-3.8
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2009-12-02T16:40:59Z

Fmoatamr: /* ns-3.7 Features Merged */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2009-12-02T16:40:45Z

Fmoatamr: /* Candidate Contributions for Inclusion in ns-3.7 */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2009-11-25T11:10:33Z

Fmoatamr: /* The ns-3.7 Bug List */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

== The ns-3.7 Bug List ==

== High Priority Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2009-11-25T11:08:49Z

Fmoatamr: /* High Priority Non-Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P2&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= High priority non blockers]

Ns-3.7

2009-11-25T11:05:18Z

Fmoatamr: /* The ns-3.7 Bug List */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

[http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= blockers list]

== High Priority Non-Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ High priority bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=341 341]
| nor ||P2||All || craigdo@ee.washington.edu||Get unexpected dropped packets when using SetSendCallback with heavy traffic
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=419 419]
| nor ||P2||All || craigdo@ee.washington.edu|| *Helper::SetAttribute* methods sometimes painful to use
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=631 631]
|nor || P2 || Linu || gjcarneiro@gmail.com || RealtimeSimulatorImpl not compatible with python bindings
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=409 409]
|nor || P2 || Linu || mathieu.lacage@sophia.inria.fr || Routing messages can exceed MTU, and fragmentation not supported
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=674 674]
|nor || P2 || All || ns-bugs@isi.edu || EIFS is not handled correctly in DcfManager::GetAccessGrantStart
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=703 703]
|nor || P2 || All || ns-bugs@isi.edu || Make OLSR robust to link/device events
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=521 521]
| nor || P2 || All || tomh@tomh.org || Ipv4 global routing inefficient
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=702 702]
|nor || P2 || All || tomh@tomh.org || Make global routing robust to link/device events
|-
|}

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-25T11:04:44Z

Fmoatamr: /* Open Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

http://www.nsnam.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ns-3&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=P1&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=

== High Priority Non-Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ High priority bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=341 341]
| nor ||P2||All || craigdo@ee.washington.edu||Get unexpected dropped packets when using SetSendCallback with heavy traffic
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=419 419]
| nor ||P2||All || craigdo@ee.washington.edu|| *Helper::SetAttribute* methods sometimes painful to use
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=631 631]
|nor || P2 || Linu || gjcarneiro@gmail.com || RealtimeSimulatorImpl not compatible with python bindings
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=409 409]
|nor || P2 || Linu || mathieu.lacage@sophia.inria.fr || Routing messages can exceed MTU, and fragmentation not supported
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=674 674]
|nor || P2 || All || ns-bugs@isi.edu || EIFS is not handled correctly in DcfManager::GetAccessGrantStart
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=703 703]
|nor || P2 || All || ns-bugs@isi.edu || Make OLSR robust to link/device events
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=521 521]
| nor || P2 || All || tomh@tomh.org || Ipv4 global routing inefficient
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=702 702]
|nor || P2 || All || tomh@tomh.org || Make global routing robust to link/device events
|-
|}

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-25T10:02:34Z

Fmoatamr: /* Net-anim */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': Merged in ns-3-dev
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Blocker bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
|}

== High Priority Non-Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ High priority bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=341 341]
| nor ||P2||All || craigdo@ee.washington.edu||Get unexpected dropped packets when using SetSendCallback with heavy traffic
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=419 419]
| nor ||P2||All || craigdo@ee.washington.edu|| *Helper::SetAttribute* methods sometimes painful to use
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=631 631]
|nor || P2 || Linu || gjcarneiro@gmail.com || RealtimeSimulatorImpl not compatible with python bindings
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=409 409]
|nor || P2 || Linu || mathieu.lacage@sophia.inria.fr || Routing messages can exceed MTU, and fragmentation not supported
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=674 674]
|nor || P2 || All || ns-bugs@isi.edu || EIFS is not handled correctly in DcfManager::GetAccessGrantStart
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=703 703]
|nor || P2 || All || ns-bugs@isi.edu || Make OLSR robust to link/device events
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=521 521]
| nor || P2 || All || tomh@tomh.org || Ipv4 global routing inefficient
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=702 702]
|nor || P2 || All || tomh@tomh.org || Make global routing robust to link/device events
|-
|}

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-25T10:01:35Z

Fmoatamr: /* ns-3.7 Features Merged */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Blocker bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
|}

== High Priority Non-Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ High priority bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=341 341]
| nor ||P2||All || craigdo@ee.washington.edu||Get unexpected dropped packets when using SetSendCallback with heavy traffic
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=419 419]
| nor ||P2||All || craigdo@ee.washington.edu|| *Helper::SetAttribute* methods sometimes painful to use
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=631 631]
|nor || P2 || Linu || gjcarneiro@gmail.com || RealtimeSimulatorImpl not compatible with python bindings
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=409 409]
|nor || P2 || Linu || mathieu.lacage@sophia.inria.fr || Routing messages can exceed MTU, and fragmentation not supported
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=674 674]
|nor || P2 || All || ns-bugs@isi.edu || EIFS is not handled correctly in DcfManager::GetAccessGrantStart
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=703 703]
|nor || P2 || All || ns-bugs@isi.edu || Make OLSR robust to link/device events
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=521 521]
| nor || P2 || All || tomh@tomh.org || Ipv4 global routing inefficient
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=702 702]
|nor || P2 || All || tomh@tomh.org || Make global routing robust to link/device events
|-
|}

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-25T10:01:20Z

Fmoatamr: /* Candidate Contributions for Inclusion in ns-3.7 */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Blocker bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
|}

== High Priority Non-Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ High priority bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=341 341]
| nor ||P2||All || craigdo@ee.washington.edu||Get unexpected dropped packets when using SetSendCallback with heavy traffic
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=419 419]
| nor ||P2||All || craigdo@ee.washington.edu|| *Helper::SetAttribute* methods sometimes painful to use
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=631 631]
|nor || P2 || Linu || gjcarneiro@gmail.com || RealtimeSimulatorImpl not compatible with python bindings
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=409 409]
|nor || P2 || Linu || mathieu.lacage@sophia.inria.fr || Routing messages can exceed MTU, and fragmentation not supported
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=674 674]
|nor || P2 || All || ns-bugs@isi.edu || EIFS is not handled correctly in DcfManager::GetAccessGrantStart
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=703 703]
|nor || P2 || All || ns-bugs@isi.edu || Make OLSR robust to link/device events
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=521 521]
| nor || P2 || All || tomh@tomh.org || Ipv4 global routing inefficient
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=702 702]
|nor || P2 || All || tomh@tomh.org || Make global routing robust to link/device events
|-
|}

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-20T10:24:07Z

Fmoatamr: /* High Priority Non-Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Blocker bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
|}

== High Priority Non-Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ High priority bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=341 341]
| nor ||P2||All || craigdo@ee.washington.edu||Get unexpected dropped packets when using SetSendCallback with heavy traffic
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=419 419]
| nor ||P2||All || craigdo@ee.washington.edu|| *Helper::SetAttribute* methods sometimes painful to use
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=631 631]
|nor || P2 || Linu || gjcarneiro@gmail.com || RealtimeSimulatorImpl not compatible with python bindings
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=409 409]
|nor || P2 || Linu || mathieu.lacage@sophia.inria.fr || Routing messages can exceed MTU, and fragmentation not supported
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=674 674]
|nor || P2 || All || ns-bugs@isi.edu || EIFS is not handled correctly in DcfManager::GetAccessGrantStart
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=703 703]
|nor || P2 || All || ns-bugs@isi.edu || Make OLSR robust to link/device events
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=521 521]
| nor || P2 || All || tomh@tomh.org || Ipv4 global routing inefficient
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=702 702]
|nor || P2 || All || tomh@tomh.org || Make global routing robust to link/device events
|-
|}

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-20T10:23:27Z

Fmoatamr: /* High Priority Non-Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Blocker bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
|}

== High Priority Non-Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ High priority bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=341 341]
| nor ||P2||All || craigdo@ee.washington.edu||Get unexpected dropped packets when using SetSendCallback with heavy traffic
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=419 419]
| nor ||P2||All || craigdo@ee.washington.edu|| *Helper::SetAttribute* methods sometimes painful to use
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=631 631]
|nor || P2 || Linu || gjcarneiro@gmail.com || RealtimeSimulatorImpl not compatible with python bindings
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=409 409]
|nor || P2 || Linu || mathieu.lacage@sophia.inria.fr || Routing messages can exceed MTU, and fragmentation not supported
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=674 674]
|nor || P2 || All || ns-bugs@isi.edu || EIFS is not handled correctly in DcfManager::GetAccessGrantStart
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=703 703]
|nor || P2 || All || ns-bugs@isi.edu || Make OLSR robust to link/device events
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=521 521]
| nor || P2 || All || tomh@tomh.org || Ipv4 global routing inefficient
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=702 702]
| nor || P2 || All || tomh@tomh.org || Make global routing robust to link/device events
|}

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-20T10:21:25Z

Fmoatamr: /* High Priority Non-Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Blocker bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
|}

== High Priority Non-Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ High priority bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=341 341]
| nor ||P2||All || craigdo@ee.washington.edu||Get unexpected dropped packets when using SetSendCallback with heavy traffic
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=419 419]
| nor ||P2||All || craigdo@ee.washington.edu|| *Helper::SetAttribute* methods sometimes painful to use
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=631 631]
|nor || P2 || Linu || gjcarneiro@gmail.com || RealtimeSimulatorImpl not compatible with python bindings
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=409 409]|nor || P2 || Linu || mathieu.lacage@sophia.inria.fr || Routing messages can exceed MTU, and fragmentation not supported
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=674 674]| nor ||P2 || All || ns-bugs@isi.edu || EIFS is not handled correctly in DcfManager::GetAccessGrantStart
|-
|}

703 nor P2 All ns-bugs@isi.edu Make OLSR robust to link/device events
521 nor P2 All tomh@tomh.org Ipv4 global routing inefficient
702 nor P2 All tomh@tomh.org Make global routing robust to link/device events

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-20T10:20:18Z

Fmoatamr: /* High Priority Non-Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Blocker bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
|}

== High Priority Non-Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ High priority bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=341 341]
| nor ||P2||All || craigdo@ee.washington.edu||Get unexpected dropped packets when using SetSendCallback with heavy traffic
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=419 419]
| nor ||P2||All || craigdo@ee.washington.edu|| *Helper::SetAttribute* methods sometimes painful to use
|-
![http://www.nsnam.org/bugzilla/show_bug.cgi?id=631 631]
|nor || P2 || Linu || gjcarneiro@gmail.com || RealtimeSimulatorImpl not compatible with python bindings
|-
409 nor P2 Linu mathieu.lacage@sophia.inria.fr Routing messages can exceed MTU, and fragmentation not supported
|-
674 nor P2 All ns-bugs@isi.edu EIFS is not handled correctly in DcfManager::GetAccessGrantStart
|-
|}

703 nor P2 All ns-bugs@isi.edu Make OLSR robust to link/device events
521 nor P2 All tomh@tomh.org Ipv4 global routing inefficient
702 nor P2 All tomh@tomh.org Make global routing robust to link/device events

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-20T10:18:18Z

Fmoatamr: /* High Priority Non-Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Blocker bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
|}

== High Priority Non-Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ High priority bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=341 341]
| nor ||P2||All || craigdo@ee.washington.edu||Get unexpected dropped packets when using SetSendCallback with heavy traffic
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=419 419]
| nor ||P2||All || craigdo@ee.washington.edu|| *Helper::SetAttribute* methods sometimes painful to use
|-
|}

631 nor P2 Linu gjcarneiro@gmail.com RealtimeSimulatorImpl not compatible with python bindings
409 nor P2 Linu mathieu.lacage@sophia.inria.fr Routing messages can exceed MTU, and fragmentation not supported

674 nor P2 All ns-bugs@isi.edu EIFS is not handled correctly in DcfManager::GetAccessGrantStart
703 nor P2 All ns-bugs@isi.edu Make OLSR robust to link/device events
521 nor P2 All tomh@tomh.org Ipv4 global routing inefficient
702 nor P2 All tomh@tomh.org Make global routing robust to link/device events

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-20T10:17:55Z

Fmoatamr: /* High Priority Non-Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Blocker bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
|}

== High Priority Non-Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ High priority bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=341 341]
| nor ||P2||All || craigdo@ee.washington.edu||Get unexpected dropped packets when using SetSendCallback with heavy traffic
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=419 419]
| nor ||P2||All || craigdo@ee.washington.edu|| *Helper::SetAttribute* methods sometimes painful to use
|-
|}

631 nor P2 Linu gjcarneiro@gmail.com RealtimeSimulatorImpl not compatible with python bindings
409 nor P2 Linu mathieu.lacage@sophia.inria.fr Routing messages can exceed MTU, and fragmentation not supported

674 nor P2 All ns-bugs@isi.edu EIFS is not handled correctly in DcfManager::GetAccessGrantStart
703 nor P2 All ns-bugs@isi.edu Make OLSR robust to link/device events
521 nor P2 All tomh@tomh.org Ipv4 global routing inefficient
702 nor P2 All tomh@tomh.org Make global routing robust to link/device events

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-20T10:15:23Z

Fmoatamr: /* High Priority Non-Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Blocker bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
|}

== High Priority Non-Blockers ==

341 nor P2 All craigdo@ee.washington.edu Get unexpected dropped packets when using SetSendCallback with heavy traffic
419 nor P2 All craigdo@ee.washington.edu *Helper::SetAttribute* methods sometimes painful to use
631 nor P2 Linu gjcarneiro@gmail.com RealtimeSimulatorImpl not compatible with python bindings
409 nor P2 Linu mathieu.lacage@sophia.inria.fr Routing messages can exceed MTU, and fragmentation not supported

674 nor P2 All ns-bugs@isi.edu EIFS is not handled correctly in DcfManager::GetAccessGrantStart
703 nor P2 All ns-bugs@isi.edu Make OLSR robust to link/device events
521 nor P2 All tomh@tomh.org Ipv4 global routing inefficient
702 nor P2 All tomh@tomh.org Make global routing robust to link/device events

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-20T10:14:30Z

Fmoatamr: /* Open Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Blocker bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
|}

== High Priority Non-Blockers ==

TBD

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-20T10:14:10Z

Fmoatamr: /* Open Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Open bugs
! Bug !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
|}

== High Priority Non-Blockers ==

TBD

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-20T10:12:51Z

Fmoatamr: /* Open Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Open bugs
! Bugzilla !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! [http://www.nsnam.org/bugzilla/show_bug.cgi?id=555 555]
| cri ||P2||All || ns-bugs@isi.edu|| DCF immediate access bug
|-
! Access point address manager
| Francesco Malandrino || [http://www.nsnam.org/bugzilla/show_bug.cgi?id=471 details] || [http://www.nsnam.org/contributed/ap-address-manager.tar.bz2 Download ap-address-manager.cc/h]
|}

341 nor P2 All craigdo@ee.washington.edu Get unexpected dropped packets when using SetSendCallback with heavy traffic
419 nor P2 All craigdo@ee.washington.edu *Helper::SetAttribute* methods sometimes painful to use
631 nor P2 Linu gjcarneiro@gmail.com RealtimeSimulatorImpl not compatible with python bindings
409 nor P2 Linu mathieu.lacage@sophia.inria.fr Routing messages can exceed MTU, and fragmentation not supported

674 nor P2 All ns-bugs@isi.edu EIFS is not handled correctly in DcfManager::GetAccessGrantStart
703 nor P2 All ns-bugs@isi.edu Make OLSR robust to link/device events
521 nor P2 All tomh@tomh.org Ipv4 global routing inefficient
702 nor P2 All tomh@tomh.org Make global routing robust to link/device events

== High Priority Non-Blockers ==

TBD

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-20T10:07:06Z

Fmoatamr: /* Open Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

{| border=1 cellspacing=0 cellpadding=3

|+ Open bugs
! Bugzilla !! Flag !!Priority !! Platform !! Reporter !! Description
|-
! Pastry DHT Port
| Charilaos Papadopoulos || early beta || [http://graphics.cs.aueb.gr/users/papado Personal Website]
|-
! Access point address manager
| Francesco Malandrino || [http://www.nsnam.org/bugzilla/show_bug.cgi?id=471 details] || [http://www.nsnam.org/contributed/ap-address-manager.tar.bz2 Download ap-address-manager.cc/h]
|}

341 nor P2 All craigdo@ee.washington.edu Get unexpected dropped packets when using SetSendCallback with heavy traffic
419 nor P2 All craigdo@ee.washington.edu *Helper::SetAttribute* methods sometimes painful to use
631 nor P2 Linu gjcarneiro@gmail.com RealtimeSimulatorImpl not compatible with python bindings
409 nor P2 Linu mathieu.lacage@sophia.inria.fr Routing messages can exceed MTU, and fragmentation not supported
555 cri P2 All ns-bugs@isi.edu DCF immediate access bug
674 nor P2 All ns-bugs@isi.edu EIFS is not handled correctly in DcfManager::GetAccessGrantStart
703 nor P2 All ns-bugs@isi.edu Make OLSR robust to link/device events
521 nor P2 All tomh@tomh.org Ipv4 global routing inefficient
702 nor P2 All tomh@tomh.org Make global routing robust to link/device events

== High Priority Non-Blockers ==

TBD

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-20T10:03:47Z

Fmoatamr: /* Open Blockers */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

341 nor P2 All craigdo@ee.washington.edu Get unexpected dropped packets when using SetSendCallback with heavy traffic
419 nor P2 All craigdo@ee.washington.edu *Helper::SetAttribute* methods sometimes painful to use
631 nor P2 Linu gjcarneiro@gmail.com RealtimeSimulatorImpl not compatible with python bindings
409 nor P2 Linu mathieu.lacage@sophia.inria.fr Routing messages can exceed MTU, and fragmentation not supported
555 cri P2 All ns-bugs@isi.edu DCF immediate access bug
674 nor P2 All ns-bugs@isi.edu EIFS is not handled correctly in DcfManager::GetAccessGrantStart
703 nor P2 All ns-bugs@isi.edu Make OLSR robust to link/device events
521 nor P2 All tomh@tomh.org Ipv4 global routing inefficient
702 nor P2 All tomh@tomh.org Make global routing robust to link/device events

== High Priority Non-Blockers ==

TBD

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-18T09:57:29Z

Fmoatamr: /* ns-3.7 Features Merged */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Merged to ns-3-dev

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

TBD

== High Priority Non-Blockers ==

TBD

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-18T09:56:55Z

Fmoatamr: /* 802.11p WiFi standards */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

== ns-3.7 Features Merged ==

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

TBD

== High Priority Non-Blockers ==

TBD

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-18T09:12:51Z

Fmoatamr: /* MPI-based parallelization */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson, Mathieu Lacage
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Will be soon merged

== ns-3.7 Features Merged ==

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

TBD

== High Priority Non-Blockers ==

TBD

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-18T08:42:34Z

Fmoatamr: /* 802.11p WiFi standards */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': Mathieu Lacage
* ''Developers'': Michael Nowatkowski
* ''Status'': Will be soon merged

== ns-3.7 Features Merged ==

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

TBD

== High Priority Non-Blockers ==

TBD

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Ns-3.7

2009-11-18T08:18:44Z

Fmoatamr: /* Waypoint mobility model */

{{TOC}}

This page summarizes the ongoing release planning for ns-3.7. The release manager is Faker Moatamri.

== Tentative ns-3.7 Release Schedule ==

# <s>October 21 -- ns-3.6 posted;</s>
# October 21 -- ns-3.7 '''''Open phase begins''''';
# November 18 -- Deadline for new feature merge;
# November 18 -- Begin the phase of small feature development and bug fixing;
# December 16 -- Small feature development and bug fixing ends;
# December 16 -- '''''Open phase ends''''';
# December 16 -- '''''Maintenance phase begins''''';>
# January 6 -- '''''Maintenance phase ends''''';
# January 6 -- '''''Code freeze phase begins''''';
# January 6 -- ns-3.7-RC1;
# January 8 -- ns-3.7-RC2;
# January 12 -- ns-3.7-RC3;
# January 15 -- ns-3.7-RC4;
# January 20 -- ns-3.7 posted;
# January 20 -- '''''Code freeze phase ends''''';
# January 20 -- ns-3.8 Open phase begins.

As described in the [[Roadmap]] there are three broad sections in the release schedule. During the open phase, people wanting to include a new feature in ns-3.7 should contact Faker and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:

* A mercurial patch, bundle or repo against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that we can apply this patch and build and run (debug and optimized as appropriate) all unit and regression tests sucessfully on all of our target machines;
* A summary of the additions you are proposing and an explanation of any changes to existing code that had to be done in order to support your feature (this will be used to genenerate release notes and will be provided to maintainers if a code review is indicated);
* Some kind of unit or system test that can be used to determine if your feature is actually working at each stage of the integration.

One of us will take a quick look at your proposed addition and determine if a code review is required. According to the ''book of instructions'' a code review requiring positive acknowledgement by maintainers is indicated if:

* Your proposed feature does not work with all models or on all platforms;
* Your feature changes pre-existing APIs;
* Your feature crosses maintainer boundaries.

Just to be safe, we will probably run a feature submission by at least one maintainer according to the general area of applicability of the feature. For example, if you submit an entirely new device driver model, as a courtesy we will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but we will take some time to allow a reasonable review.

The open phase is divided into two parts: new feature merge period and small feature development and bug fixing.

During the new feature merge period we can:
* Review the code that might be merged
* Clean up the bug tracker: solve as much bugs as possible
* Merge the new features that has +1 and from maintainers

After November 18th, the new feature merge period ends and small feature development and bug fixes begins. During the latter, no more merges are accepted and we can:
* Accept limited, small, self contained changes/features to ns-3-dev and to merged new features. As specified before, no more merges are accepted.
* Review the code to be merged for next releases
* Cleanup the ns-3-dev bug tracker, solve as much bugs as possible

The end of the small feature development and bug fixes coincides (December 16th) with the beginning of the maintenance phase. No new features may be added, but the maintainers may check in fixes to bugs; and people with new features that have been accepted and previously merged may fix bugs in existing features. Please don't try to sneak in more new features or you may have your whole feature set removed at the release manager's discretion. You can ask if you want to add small, self-contained features, but there are no guarantees that we will okay them.

On January 6th, 2010, we are going to enter the code freeze phase. This indicates that we are in the final stages of the release and our primary goal is stability. During the code freeze phase, only P1 bugfixes will be allowed to be checked in. Our ''goal'' will be to reduce the number of P1 bugs to zero before the release of ns-3.7.

'''''We will reserve the right to veto (and remove) any new feature addition if it begins to cause problems and looks like it threatens the stability of the release at any time in the release process.'''''

== Candidate Contributions for Inclusion in ns-3.7 ==

=== Underwater Acoustic Network Device ===

* ''review location'': http://codereview.appspot.com/87043
* ''reviewer(s)'': Craig Dowell, Faker Moatamri
* ''status'': postponed to NS-3.8
* ''Developer'': Leonard Tracy
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-June/006148.html

=== WiMAX ===

* ''code location'': http://code.nsnam.org/iamine/ns-3-wimax-release/
* ''reviewers'': Faker Moatamri, Mathieu Lacage, Tom Henderson
* ''Developer'': Amine Ismail
* ''status'': planning to merge soon
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-August/006329.html

=== NHDP ===
* ''Code'': No available code for the moment
* ''Developer'': Tom Wambold
* ''Status'': waiting to the code to be ready to review

=== MPI-based parallelization ===

* ''review location'': http://codereview.appspot.com/109068
* ''code location'': http://code.nsnam.org/jpelkey3/ns-3-distributed
* ''reviewers'': Faker Moatamri, Craig Dowell, Tom Henderson
* ''Developer'': Josh Pelkey
* ''Status'': needs other reviews
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006927.html

=== Net-anim ===

* ''Review location'': http://codereview.appspot.com/117051
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developers'': George Riley and Josh Pelkey
* ''Status'': waiting for fixes after Tom's review
* ''Background'': http://mailman.isi.edu/pipermail/ns-developers/2009-November/006914.html

=== Internet stack roadmap ===
* Work on various parts of the TCP/IP stack is tracked [[Internet-stack-maintenance | on this wiki page]]

=== NAT traversal ===

* ''background'': http://www.nsnam.org/wiki/index.php/GSOC2009NetworkAddressTranslation

=== 802.11n block ack ===

* ''Review location'': http://codereview.appspot.com/144050
* ''Reviewers'': Faker Moatamri, Nicola Baldo, Andrey Mazo, Andreev Kirill, Mathieu Lacage
* ''Developer'': Mirko Blanchi
* ''Status'': waiting for mathieu's review

=== IPv6 Extension and Option Headers ===

* ''Review location'': http://codereview.appspot.com/144048
* ''Reviewers'': Faker Moatamri
* ''Developers'': Sebastien Vincent, Fabian Mauchle
* ''Status'': Needs more reviews

=== 802.11p WiFi standards ===

* ''Review location'': http://codereview.appspot.com/152058/show
* ''Reviewers'': TBD
* ''Developers'': Michael Nowatkowski
* ''Status'': Posted for review on November 10.

== ns-3.7 Features Merged ==

=== Waypoint mobility model ===

* ''review location'': http://codereview.appspot.com/144064/show
* ''Reviewers'': Mathieu Lacage, Faker Moatamri
* ''Developer'': Phillip Sitbon
* ''Status'': merged into mainstream, needs tests and examples from Phillip
* ''Features'':
** Provides a waypoint type to correlate time and position, and
** A waypoint-based mobility model that calculates positions at and in between waypoints when queried.
** Uses about half as much memory as the equivalent event-based method(velocity/direction updates), mostly by removing each waypoint when it is reached.
** Faster: caches the current position of each node at a given time step, requiring N less floating-point calculations for distances between every pair (N being the number of simulation nodes).

=== Ad Hoc On Demand Distance Vector (AODV) Routing (RFC 3561) ===

* ''Code location'': https://forge.iitp.ru/hgprojects/ns3aodv/
* ''Review location'': http://codereview.appspot.com/115075/show
* ''Reviewers'': Faker Moatamri, Tom Henderson
* ''Developer'': Pavel Boyko
* ''Status'': Corrections made, waiting for +1s?
* ''background'': http://mailman.isi.edu/pipermail/ns-developers/2009-September/006497.html
* ''Features'':
** Added the AODV model
** The Duplicate Packet Detection (DPD) model has been factored out of AODV, for use by other protocols
** Proposal to create a src/routing/manet directory, which would include AODV and the new DPD module, but also would argue for moving olsr and packetbb to this new directory
** Extensions to IPv4 Ping application, including the ability to configure different ping sizes and time intervals (via new attributes)
** Contrib/average.h -- almost trivial template class for averaging.

== The ns-3.7 Bug List ==

At the completion of the ns-3.6 release, all P2 bugs will be promoted to P1 status.

== Open Blockers ==

TBD

== High Priority Non-Blockers ==

TBD

----
[[User:Craigdo|Craigdo]] 02:16, 22 October 2009 (UTC)

Contributed Code

2009-11-17T09:28:15Z

Fmoatamr: /* Contributed code not maintained by the project */

{{TOC}}
There are several ways to contribute code to ns-3:
# [http://www.nsnam.org/contributing.html#contribute Contribute to the main tree]
# Send contributed code to one of the maintainers, for archiving on the project website (and listing here)
# Maintain or archive your code at your own site and add a link here

== Contributed code under review for the main tree ==

The preferred place for contributed code to end up is in our main tree. See section 2 of the
[[Current_Development]] page for a listing of all code that is under review for the main tree.

== Contributed code in src/contrib ==

Please note that the src/contrib/ directory in ns-3 is a place for experimental code or code that the maintainers have not yet committed to accepting into the main tree. Some ns-3 code (such as statistics code) started out by living in the src/contrib/ directory while it was being evaluated. This is an alternate target for contributing your code.

== Contributed code not maintained by the project ==

Not all code will end up being merged-- some is being maintained by third party sites or maintainers. This section can be used to list this other code. Note also that if you want the ns-3 project to maintain a tarball of your scripts or models for long-term archiving, we can list it here.

{| border=1 cellspacing=0 cellpadding=3

|+ Contributions
! Contribution !! Contributor !! Status !! Link
|-
! Pastry DHT Port
| Charilaos Papadopoulos || early beta || [http://graphics.cs.aueb.gr/users/papado Personal Website]
|-
! Access point address manager
| Francesco Malandrino || [http://www.nsnam.org/bugzilla/show_bug.cgi?id=471 details] || [http://www.nsnam.org/contributed/ap-address-manager.tar.bz2 Download ap-address-manager.cc/h]
|}

== Archived repositories ==

These ns-3 repositories may be of interest to future users; many of them are prototypes that were never merged to the main tree and have been abandoned.

* [http://www.nsnam.org/contributed/ns-3-swig.tar.bz2 SWIG bindings for ns-3 (Craig Dowell)]
* [http://www.nsnam.org/contributed/ns-3-nam.tar.bz2 nam (ns-2 network animator) for ns-3 (Mathieu Lacage)]
* [http://www.nsnam.org/contributed/ns-3-yans.tar.bz2 yans port to ns-3 (Mathieu Lacage)]
* [http://www.nsnam.org/contributed/ns-3-netlink.tar.bz2 ns-3 netlink sockets (Liu Jian)]
* [http://www.nsnam.org/contributed/quagga-porting.tar.bz2 quagga porting (Liu Jian)]
* [http://www.nsnam.org/contributed/ns-3-para.tar.bz2 ns-3 parallelized branch (Hagen Paul Pfeifer)]
* [http://www.nsnam.org/contributed/ns-3-para-mpi.tar.bz2 MPI infrastructure (Hagen Paul Pfeifer)]
* [http://www.nsnam.org/contributed/ns-3-worker.tar.bz2 worker parallelization (Hagen Paul Pfeifer)]
* [http://www.nsnam.org/contributed/ns-3-dev-http.tar.bz2 toy http model (Raj Bhattacharjea)]
* [http://www.nsnam.org/contributed/ns-3-wifi-scanning.tar.bz2 experimental wifi scanning (Gustavo Carneiro)]

Contributed Code

2009-11-17T08:51:50Z

Fmoatamr: /* Contributed code not maintained by the project */

{{TOC}}
There are several ways to contribute code to ns-3:
# [http://www.nsnam.org/contributing.html#contribute Contribute to the main tree]
# Send contributed code to one of the maintainers, for archiving on the project website (and listing here)
# Maintain or archive your code at your own site and add a link here

== Contributed code under review for the main tree ==

The preferred place for contributed code to end up is in our main tree. See section 2 of the
[[Current_Development]] page for a listing of all code that is under review for the main tree.

== Contributed code in src/contrib ==

Please note that the src/contrib/ directory in ns-3 is a place for experimental code or code that the maintainers have not yet committed to accepting into the main tree. Some ns-3 code (such as statistics code) started out by living in the src/contrib/ directory while it was being evaluated. This is an alternate target for contributing your code.

== Contributed code not maintained by the project ==

Not all code will end up being merged-- some is being maintained by third party sites or maintainers. This section can be used to list this other code. Note also that if you want the ns-3 project to maintain a tarball of your scripts or models for long-term archiving, we can list it here.

{| border=1 cellspacing=0 cellpadding=3

|+ Contributions
! Contribution !! Contributor !! Status !! Link
|-
! Pastry DHT Port
| Charilaos Papadopoulos || early beta || [http://graphics.cs.aueb.gr/users/papado Personal Website]
|-
! Access point address manager
| Francesco Malandrino || early beta || [http://www.nsnam.org/contributed/ap-address-manager.tar.bz2 Download ap-address-manager.cc/h]
|}

== Archived repositories ==

These ns-3 repositories may be of interest to future users; many of them are prototypes that were never merged to the main tree and have been abandoned.

* [http://www.nsnam.org/contributed/ns-3-swig.tar.bz2 SWIG bindings for ns-3 (Craig Dowell)]
* [http://www.nsnam.org/contributed/ns-3-nam.tar.bz2 nam (ns-2 network animator) for ns-3 (Mathieu Lacage)]
* [http://www.nsnam.org/contributed/ns-3-yans.tar.bz2 yans port to ns-3 (Mathieu Lacage)]
* [http://www.nsnam.org/contributed/ns-3-netlink.tar.bz2 ns-3 netlink sockets (Liu Jian)]
* [http://www.nsnam.org/contributed/quagga-porting.tar.bz2 quagga porting (Liu Jian)]
* [http://www.nsnam.org/contributed/ns-3-para.tar.bz2 ns-3 parallelized branch (Hagen Paul Pfeifer)]
* [http://www.nsnam.org/contributed/ns-3-para-mpi.tar.bz2 MPI infrastructure (Hagen Paul Pfeifer)]
* [http://www.nsnam.org/contributed/ns-3-worker.tar.bz2 worker parallelization (Hagen Paul Pfeifer)]
* [http://www.nsnam.org/contributed/ns-3-dev-http.tar.bz2 toy http model (Raj Bhattacharjea)]
* [http://www.nsnam.org/contributed/ns-3-wifi-scanning.tar.bz2 experimental wifi scanning (Gustavo Carneiro)]

Contributed Code

2009-11-17T08:47:55Z

Fmoatamr: /* Contributed code not maintained by the project */

{{TOC}}
There are several ways to contribute code to ns-3:
# [http://www.nsnam.org/contributing.html#contribute Contribute to the main tree]
# Send contributed code to one of the maintainers, for archiving on the project website (and listing here)
# Maintain or archive your code at your own site and add a link here

== Contributed code under review for the main tree ==

The preferred place for contributed code to end up is in our main tree. See section 2 of the
[[Current_Development]] page for a listing of all code that is under review for the main tree.

== Contributed code in src/contrib ==

Please note that the src/contrib/ directory in ns-3 is a place for experimental code or code that the maintainers have not yet committed to accepting into the main tree. Some ns-3 code (such as statistics code) started out by living in the src/contrib/ directory while it was being evaluated. This is an alternate target for contributing your code.

== Contributed code not maintained by the project ==

Not all code will end up being merged-- some is being maintained by third party sites or maintainers. This section can be used to list this other code. Note also that if you want the ns-3 project to maintain a tarball of your scripts or models for long-term archiving, we can list it here.

{| border=1 cellspacing=0 cellpadding=3

|+ Contributions
! Contribution !! Contributor !! Status !! Link
|-
! Pastry DHT Port
| Charilaos Papadopoulos || early beta || [http://graphics.cs.aueb.gr/users/papado Personal Website]
|-
! Pastry DHT Port
| Charilaos Papadopoulos || early beta || [http://graphics.cs.aueb.gr/users/papado Personal Website]
|}

== Archived repositories ==

These ns-3 repositories may be of interest to future users; many of them are prototypes that were never merged to the main tree and have been abandoned.

* [http://www.nsnam.org/contributed/ns-3-swig.tar.bz2 SWIG bindings for ns-3 (Craig Dowell)]
* [http://www.nsnam.org/contributed/ns-3-nam.tar.bz2 nam (ns-2 network animator) for ns-3 (Mathieu Lacage)]
* [http://www.nsnam.org/contributed/ns-3-yans.tar.bz2 yans port to ns-3 (Mathieu Lacage)]
* [http://www.nsnam.org/contributed/ns-3-netlink.tar.bz2 ns-3 netlink sockets (Liu Jian)]
* [http://www.nsnam.org/contributed/quagga-porting.tar.bz2 quagga porting (Liu Jian)]
* [http://www.nsnam.org/contributed/ns-3-para.tar.bz2 ns-3 parallelized branch (Hagen Paul Pfeifer)]
* [http://www.nsnam.org/contributed/ns-3-para-mpi.tar.bz2 MPI infrastructure (Hagen Paul Pfeifer)]
* [http://www.nsnam.org/contributed/ns-3-worker.tar.bz2 worker parallelization (Hagen Paul Pfeifer)]
* [http://www.nsnam.org/contributed/ns-3-dev-http.tar.bz2 toy http model (Raj Bhattacharjea)]
* [http://www.nsnam.org/contributed/ns-3-wifi-scanning.tar.bz2 experimental wifi scanning (Gustavo Carneiro)]

Ns-3.7

2009-11-16T16:45:27Z

Fmoatamr: /* Net-anim */

Ns-3.7

2009-11-16T16:45:01Z

Fmoatamr: /* Underwater Acoustic Network Device */

Ns-3.7

2009-11-16T15:57:03Z

Fmoatamr: /* AODV */

Ns-3.7

2009-11-16T15:49:02Z

Fmoatamr: /* AODV */

Ns-3.7

2009-11-16T15:48:29Z

Fmoatamr: /* AODV */

Ns-3.7

2009-11-16T15:47:33Z

Fmoatamr: /* AODV */

Ns-3.7

2009-11-16T15:45:47Z

Fmoatamr: /* ns-3.7 Features Merged */