This page summarizes the ongoing release planning for the third stable release of ns-3.
- ns-3-dev is currently in the maintenance phase of the ns-3.3 release. Only bugfixes for bugs reported in the tracker are allowed.
- The first release candidate for ns-3.3 is scheduled for release on December 1, 2008
- ns-3.3 is scheduled for release in December 17, 2008.
The Hot List
ns-3.3 is currently in the maintenance phase of the release. The next phase, the code-freeze phase starts on December 1, 2008. By definition, all priority one bugs should be fixed by that time. As I type this, it is November 17, and we have nine working days left until code freeze (seven days in the U.S. due to the Thanksgiving holiday).
As soon as ns-3.2.1 is released, the bugs in the tracker marked as priority two will be elevated to priority one and therefore be blockers for ns-3.3 as defined. We have accumulated quite a list of such bugs. I have broken out the list under the maintainers who are responsible for the bugs. This is a friendly reminder that this list really needs to be close to zero bugs by November 30.
- 250 Tcp breaks if you set the delackcount > 2
- 341 Get unexpected dropped packets when using SetSendCallback with heavy traffic
- 358 calling listen on non-closed TCP sockets sends resets, should fail and do nothing
- 365 TcpSocketImpl::Recv returns 0 without setting m_errno
- 392 Example star.cc confuses TCP
- 410 Doxygen is not picking up class OnOffHelper
- 411 OnOffApplication::OnTime does not work
- 348 regression tests do not work in private or disconnected networks
- 289 CommandLine::AddValue is not wrapped
- 325 regression code should be moved into regression/wscript
- 387 Build fails with junk subdirectories in "scratch" directory
- 407 OLSR may select wrong interface in MID context
- 413 python bindings not portable to OS X
- 66 improve granularity of GlobalRouteManager::PopulateRoutes
- 114 global routing doesn't handle multi-hop layer-2 subnets
- 187 Need 'perfect' ARP
- 241 Trace sources not clearly documented, trace sinks not clearly documented
- 263 XxxAddress::ConvertFrom are prone to subtle bugs
383 Please make _all_ header structures public-- Fixed
391 Example csma-star kills global routing-- Fixed
401 add InternetStackHelper::EnableAscii ()-- Fixed
403 Ipv4AddressHelper cannot assign /32 addresses-- Fixed
404 ErrorModel attribute name is not consistent across devices-- Fixed
- 188 global routing does not handle ip aliasing
- 400 Wifi Muti-Hop Network not forwaring packets (atleast ARP)
- 406 GlobalRouteManager behaviour after Ipv4 interface SetDown and SetUp procedure
- 215 Node names patch
- 218 wifi PHY base class must be virtualized and subclass renamed
- 230 Simulator::Now() Updating and Simulator::Stop()
- 257 log time printer, can we optionally support output of time in seconds?
- 395 log distance propagation loss model complex to use.
- 396 Weird WiFi error state with STA slowing approaching the wifi range of an AP
- 397 Custom WifiModes apparently not possible in infrastructure mode
- 398 NqstaWifiMac does not filter received frames by BSSID
- 405 wifi log messages improvements
- 408 No duplicate filtering for managament frames
- 409 Simulation fails depending on number of wireless nodes
- 412 Extend number of template parameters in xxxCallback classes
- 320 getsockname returns a port number in network byte order
- 356 tcp-nsc-lfn fails with --valgrind selected
The Release Manager
Craig Dowell (craigdo at ee.washington.edu) is the release manager for ns-3.3 and is the contact for any release issues.
The ns-3.3 Release Schedule
ns-3 releases are based on date-driven schedules as opposed to feature-driven schedules. We decide on a release date and then the release manager works backward to define windows during which time certain activites related to the release can happen. This has been done for ns-3.3 and the important milestones are:
- September 22 -- ns-3.2 posted;
- September 22 -- ns-3.3 Open phase begins;
- October 20 -- Recommended cutoff for new feature submission;
- October 27 -- Deadline for new feature submissions that require design review;
- November 3 -- Approved new feature ready-for-merge deadline;
- November 3 -- Late merge period begins (Merge Week Begins);
- November 10 -- Late merge period ends;
- November 10 -- Open phase ends;
- November 10 -- Maintenance phase begins;
- December 1 -- Maintenance phase ends;
- December 1 -- Code freeze phase begins;
- December 1 -- ns-3.3-RC1;
- December 4 -- ns-3.3-RC2;
- December 8 -- ns-3.3-RC3;
- December 11 -- ns-3.3-RC4;
- December 17 -- ns-3.3 posted;
- December 17 -- Code freeze phase ends;
- December 17 -- ns-3.4 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.3 should contact craigdo and arrange to have their features merged into ns-3-dev. You will be expected to provide the following:
- A mercurial patch or bundle against the current version of ns-3-dev that contains your proposed feature addition. You need to make sure that I 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 regression test that I can use to determine if your feature is actually working at each stage of the integration.
I 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, I 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 I will run this submission by the maintainers of the current devices. The maintainers won't have any responsibility to positively ack the submission, but I will take some time to allow a reasonable review.
I will coordinate new feature merges beginning at the start of the open phase (September 22, 2008). The absolute final deadline for feature inclusion in ns-3.3 is the start of the "Late merge period." This is the time during which I merge the code from all of those people who have waited until the last minute and work out any system integration issues that pop up. If you miss the start of the late merge period, or have a feature that is not design-reviewed by the start of the late merge period, well, sorry. You get to wait until the ns-3.4 open period to try again.
The end of the late merge period coincides 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 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 me if you want to add small, self-contained features, but there are no guarantees that I will okay them.
On December 1st, 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. I will begin my daily annoying emails listing all of the priority one bugs that are outstanding. Our goal will be to reduce the number of P1 bugs to zero before the release of ns-3.3.
I 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.
Candidates for Merge into ns-3.3
As you can see in the Roadmap, we have identified several candidates for inclusion in ns-3.3. As time passes, I will add more status regarding the progress of these new features.
- IPv6 Address Support -- Merged
- Emulation Mode Support -- Merged
- ICMP Support -- Merged
Build System Refactoring-- Dropped from ns-3.3
IPv4/Routing Refactoring + Basic IPv6 Support-- Dropped from ns-3-3
Random Number Generator and RandomVariable Changes-- Dropped from ns-3.3
IPv6 Address Support
Status as of November 7, 2008
IPv6 Address Support merged into ns-3-dev.
Emulation Mode Support
Status as of November 5, 2008
Emulation Mode Support merged into ns-3-dev.
Status as of October 29, 2008
ICMP Support merged into ns-3-dev.
Craigdo 05:52, 18 November 2008 (UTC)