[Ns-developers] ns-3.3 Release Planning -- Code Freeze is inEffect

[Raj Bhattacharjea]

On Tue, Dec 2, 2008 at 3:10 PM, <craigdo at ee.washington.edu> wrote:

> [ ... ]
>
> > If I may offer a suggestion, I think it might be better to
> > have a ns-3.3 branch besides a ns-3-dev:
>
> [ ... ]
>
> We have talked about this and I suspect it will happen; but to be
> completely
> and absolutely blunt, there was enough chaos in the last major release that
> I pushed back hard at the idea of adding to this release yet another
> opportunity for confusion regarding what was checked into which repo and
> when and how and when it was all sequenced, integrated and tested.
>
>
There is plenty of time to think on this, since Gustavo suggests this for
ns3.4.  But, we have been snapshotting the dev branch as a release since we
started, with the exception of 3.2.1, which was released as Gustavo
suggested.  It keeps things simpler.  We can hold our patches in our pockets
(or start "experimental" branches to track our changes) until the freeze is
over.

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