[Ns-developers] ns-3.2.1-RC3 final release candidate

[Raj Bhattacharjea]

On Thu, Nov 6, 2008 at 11:19 AM, Gustavo Carneiro <gjcarneiro at gmail.com>wrote:

> This build fix is not available in RC3:
>
> c4acb0e1fd28: "Work around a WAF bug in failing to recognize GCC while
> detecting CXXFLAGS for compiling Python extensions."
>
> Although I cannot reproduce the compilation problem with my compiler, the
> fact is that the flag -fno-strict-aliasing is missing when compiling Python,
> at least in theory.  The patch fixes it.
>

This has been a more lax release cycle than what Craig usually runs (no hard
deadlines, no "freezes", etc.), because, in my opinion, this release is
fundamentally different (no new features, bugfixes only).  That said, there
needs to be a freeze at some point, because otherwise, since we are be
continuously checking in bug fixes to the dev branch, we would continue to
patch these into 3.2.1-RC(x) and never actually make a release.  The plan
was to release 3.2.1 tomorrow, and I don't want to slip again...

BUT, my inclination as release manager is to include this as the final fix
in the release which will be made tomorrow, just without another release
candidate between now and then.  Does anyone object to this?  It makes sense
to me because it seems that this is a build breaking bug for python bindings
on certain setups.

-- 
Raj Bhattacharjea
Georgia Institute of Technology
School of Electrical and Computer Engineering
Ph.D. Candidate
Systems Analyst
404.894.2955