Ns-3.6: Difference between revisions
| (One intermediate revision by the same user not shown) | |||
| Line 26: | Line 26: | ||
# <s>October 21 -- ns-3.6 posted;</s> | # <s>October 21 -- ns-3.6 posted;</s> | ||
# <s>October 21 -- '''''Code freeze phase ends''''';</s> | # <s>October 21 -- '''''Code freeze phase ends''''';</s> | ||
# October 21 -- ns-3.7 Open phase begins. | # <s>October 21 -- ns-3.7 Open phase begins.</s> | ||
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.6 should contact craigdo and arrange to have their features merged into ns-3-dev. You will be expected to provide the following: | 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.6 should contact craigdo and arrange to have their features merged into ns-3-dev. You will be expected to provide the following: | ||
| Line 194: | Line 194: | ||
Awarded to Pavel Boyko for stepping up and converting lots of unit tests to the new framework; and to Andrey Mazo for stepping up and sweeping the tutorial for typos and required changes. We who are about to release, salute you! | Awarded to Pavel Boyko for stepping up and converting lots of unit tests to the new framework; and to Andrey Mazo for stepping up and sweeping the tutorial for typos and required changes. We who are about to release, salute you! | ||
---- | ---- | ||
[[User:Craigdo|Craigdo]] | [[User:Craigdo|Craigdo]] 01:07, 22 October 2009 (UTC) | ||
Latest revision as of 01:09, 22 October 2009
Main Page - Roadmap - Summer Projects - Project Ideas - Developer FAQ - Tools - Related Projects
HOWTOs - Installation - Troubleshooting - User FAQ - Samples - Models - Education - Contributed Code - Papers
This page summarizes the ongoing release planning for ns-3.6. The release manager is Craig Dowell.
ns-3.6 is now complete and released. See Ns-3.7 for a tentative ns-3.7 release schedule.
The ns-3.6 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.6 and the important milestones are:
July 4 -- ns-3.5 posted;July 5 -- ns-3.6 Open phase begins;August 26 -- Recommended cutoff for new feature submission;September 2 -- Deadline for new feature submissions that require design review;September 9 -- Approved new feature ready-for-merge deadline;September 9 -- Late merge period begins (Merge Week Begins);September 16 -- Late merge period ends;September 16 -- Open phase ends;September 16 -- Maintenance phase begins;>September 30 -- Maintenance phase ends;>October 7 -- Maintenance phase ends;October 7 -- Code freeze phase begins;October 8 -- ns-3.6-RC1;October 12 -- ns-3.6-RC2;October 15 -- ns-3.6-RC3;October 19 -- ns-3.6-RC4;October 21 -- ns-3.6 posted;October 21 -- Code freeze phase ends;October 21 -- ns-3.7 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.6 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, bundle or repo 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 late merge period (September 16, 2009). 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 do wait until the last moment, you are not guaranteed to get your code into ns-3.6 even if it is perfect and completely reviewed. This is a first-in first-out process (with possible priority boosts based on inputs from higher up) and will continue as long as resources allow; but don't expect any results. 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.7 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 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 me if you want to add small, self-contained features, but there are no guarantees that I will okay them.
On September 30th, 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.6.
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.
Candidate Contributions for Inclusion in ns-3.6
The ns-3.6 open phase has ended. Nor further contributions will be accepted.
ns-3.6 Features Merged
Nix-Vector Routing
- contact: George Riley, Josh Pelkey
- status: Merge Completed September 18, 2009
NetAnim Animator Support
- contact: George Riley, Josh Pelkey
- status: Merge Completed September 18, 2009
Flow Monitor
- contact: Gustavo Carneiro
- status: Merge Completed September 16, 2009
Multi-Channels in YANS Wifi Phy
- contact: Ramon Bauza
- status: Merge Completed September 15, 2009
802.11s Mesh Model
- contact: Pavel Boyko
- status: Merged September 14, 2009
PacketBB (RFC 5444)
- contact: Tom Wambold
- status: Merged September 13, 2009
Testing and Validation Framework
- contact: Craig Dowell
- status: Merged September 12, 2009
Minstrel Rate Control Algorithm
- contact: Duy Nguyen
- status: Merged
IPv6 models
- IPv6 interface;
- IPv6 layer;
- IPv6 raw socket;
- Static IPv6 routing;
- ICMPv6 layer;
- Some ICMPv6 error messages;
- Neighbor Discovery Protocol (NS/NA, RS/RA, redirection);
- Ping6 application (send Echo request);
- Radvd application (send RA);
- Examples (ping6, simple-routing-ping6, radvd, radvd-two-prefix, icmpv6-redirect).
AthstatsHelper
- Nicola Baldo contribution;
- Enables the wifi device to produce periodic reports similar to madwifi athstats.
The List of ns-3.6 Open P1 Bugs
The following bugs must, by definition, be addressed before ns-3.6 ships.
None.
The list of P1 bugs in Bugzilla can be found here
P1 Bugs Assigned to Craig Dowell
Bug 612 tri P1 All craigdo@ee.washington.edu NEW example scriptsBug 648 tri P1 All craigdo@ee.washington.edu NEW Missing Doxygen for Several HelpersBug 669 nor P1 All craigdo@ee.washington.edu NEW main-packet-printer brokenBug 675 nor P1 All craigdo@ee.washington.edu NEW Two Unit Test EnvironmentsBug 680 nor P1 All ns-bugs@isi.edu NEW Net-anim trace source needs config supportBug 714 blo P1 All ns-bugs@isi.edu NEW TestSute ns3-tcp-cwnd fails
P1 Bugs Assigned to Tom Henderson
Bug 624 nor P1 All tomh@tomh.org NEW Unable to modify packet tag in RouteInput ()Bug 643 nor P1 All tomh@tomh.org NEW Interference Helper may not calculate noise interference properlyBug 651 nor P1 All tomh@tomh.org NEW Ipv4StaticRouting doesn't work stand-alone: can't deliver local packetsBug 676 tri P1 All tomh@tomh.org NEW Align Ipv{4,6}L3Protocol Rx/Tx/Drop signaturesBug 678 nor P1 All tomh@tomh.org NEW InternetStackHelper::SetRoutingHelper does evil thingsBug 704 min P1 All tomh@tomh.org NEW ns3-wifi-propagation-loss-models
P1 Bugs Assigned to Andrey Mazo
P1 Bugs Assigned to Duy Nguyen
P1 Bugs Assigned to George Riley / Josh Pelkey
Bug 424 blo P1 All riley@ece.gatech.edu NEW TCP FIN notification callback neededBug 426 blo P1 All riley@ece.gatech.edu NEW TCP: close does not send RSTBug 559 blo P1 All riley@ece.gatech.edu REOP TcpSocketImpl doesnt free endpoint quickly enough after being closedBug 615 blo P1 All riley@ece.gatech.edu NEW TCP does not respond with RST to non-listening portBug 647 blo P1 All riley@ece.gatech.edu NEW Ns-3 implementation of TCP fails to produce limited-queue CW sawtoothBug 663 blo P1 All riley@ece.gatech.edu NEW RST from remote TCP crashes ns-3 TCPBug 664 blo P1 All ns-bugs@isi.edu NEW memory fault/dangling pointer problems in tcp-socket-impl.cc, with suggested fixesBug 682 nor P1 All ns-bugs@isi.edu NEW UdpEchoClient does not reset socket on StopApplicationBug 697 blo P1 All riley@ece.gatech.edu NEW TCP "Sent" callback reports wrong count
Homeless P1 Bugs
None.
The List of ns-3.6 Resolved P1 Bugs
Bug 555 nor P1 All ns-bugs@isi.edu NEW DCF immediate access bugBug 624 nor P1 All tomh@tomh.org NEW Unable to modify packet tag in RouteInput ()Bug 643 nor P1 All tomh@tomh.org NEW Interference Helper may not calculate noise interference properlyBug 645 nor P1 All tjkopena@cs.drexel.edu NEW patch fixes for opening stats file with OMNeT++Bug 648 tri P1 All craigdo@ee.washington.edu NEW Missing Doxygen for Several HelpersBug 666 tri P1 All dnlove@gmail.com NEW wifi rates off by factor of 1000000 in ascii outputBug 669 nor P1 All craigdo@ee.washington.edu NEW main-packet-printer brokenBug 680 nor P1 All ns-bugs@isi.edu NEW Net-anim trace source needs config supportBug 682 nor P1 All ns-bugs@isi.edu NEW UdpEchoClient does not reset socket on StopApplicationBug 704 min P1 All tomh@tomh.org NEW ns3-wifi-propagation-loss-modelsBug 710 blo P1 All ns-bugs@isi.edu NEW simple-wifi-frame-aggregation fails valgrindBug 712 blo P1 All ns-bugs@isi.edu NEW TestSute ns3-tcp-cwnd crashes under valgrindBug 713 blo P1 All ns-bugs@isi.edu NEW TestSute ns3-tcp-interoperability crashes under valgrind
High Priority Non-Blockers
The following bugs would be nice-to-have before ns-3.6 ships. If all of the P1 bugs are fixed, we will begin to address these bugs.
None.
The Incredibly Incredible and Fabulously Fabulous ns-3.6 Contribution Awards
The coveted ns-3.6 Release Contribution Awards have been announced for the pre-RC phase of the release. The Nobel Prize winners will just have to take a back seat to:
Awarded to Pavel Boyko for stepping up and converting lots of unit tests to the new framework; and to Andrey Mazo for stepping up and sweeping the tutorial for typos and required changes. We who are about to release, salute you!
Craigdo 01:07, 22 October 2009 (UTC)