[Ns-developers] Ns-3.2 Daily Bug Status for Tuesday, September 9, 2008

[craigdo@ee.washington.edu]

Dear All,

News:
=====

See "Next Steps."  I think we need to slip the release.

Comments:
=========

The system is still having build problems as of Tuesday at 1730.  I still
cannot build and run the expected suite on all of our primary supported
systems.  Today has seen several new problems uncovered and fixed; but we're
still not there yet.

I was going to release ns-3.2-RC2 on Monday.  I tried again today, but this
has now slipped until tomorrow.  I might be able to get something working
tonight, but I don't want to try and push it out with essentially no
testing.  I will try again tomorrow to see if we can get it together.

Everyone needs to make sure all of their code works on all officially
supported platforms with a clean check-out in every case; and they need to
do it yesterday.

Bugs:
=====

As of Tuesday evening (PST), September 9, 2008, we have two P1 bugs filed
against ns-3.2-RC1:

Bug 327 -- need 'conditional' regression tests 

           Status:  We desperately need nsc regression tests.  This enables
them.

Bug 328 -- NSC Doesn't symlink linux-2.6.18.so 

           Status:  NSC example asserts.  Sam has a patch.

Progress / Closed Bugs:
=======================

We have closed the following bugs relating to ns-3.2-RC1:

Bug 277 -- star topologies are painful to create
Bug 306 -- nsc: -ldl dependency problem when GtkConfigStore disabled 
Bug 313 -- regression test fails: test wifi-wired-bridging 
Bug 322 -- --enable-nsc attempts to use mercurial to download nsc ...
Bug 324 -- Regression tests refuse to run under MinGW 

Next Steps:
===========

I will post an ns-3-RC2 as soon as I can get the primary release platforms
running all of the expected software.  This has not yet happened.  It is
clear to me that some of the code in question has *never been run*.  This is
"Very Bad" (TM).

I believe we need to slip ns-3-RC3 until Monday, September 15.  This is
because of all of the instabilities we have seen over the past few days.  We
need to see some hint of stability before proceeding.

This, in turn, means that I think the release of ns-3.2 can happen no sooner
than Wednesday, September 17.  Since it is often the case that the more
problems we see, the more problems we will have in the future, I suggest
delaying until Friday, September 19, the release of ns-3.2 (we can beat on
RC3 during the extra time).  I really want to see a period of stability
before the release, and I am extremely uncomfortable with the state of this
product right now.

Regards,

-- Craig