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

[Gustavo Carneiro]

2008/12/2 <craigdo at ee.washington.edu>

> Dear All,
>
> This is a reminder that we are in the process of putting together our next
> release -- ns-3.3.  We are now in the code-freeze phase of release process.
> Code freeze means that the ns-3-dev is locked down, and all checkins to
> ns-3-dev must be in response to P1 bugs and any checkins must be
> coordinated
> with your friendly neighborhood release manager (me).  Please, no checkins
> without approval -- it might not seem like it, but uncoordinated checkins
> can cause a surprisingly large amount of pain over here.


If I may offer a suggestion, I think it might be better to have a ns-3.3
branch besides a ns-3-dev:

  ns-3.3: receives commits only approved by the release manager;

  ns-3-dev: receives assorted commits (minor new features), and someone
regularly pulls in fixes from ns-3.3.

This way approved bug fixes are only committed to ns-3.3, and mercurial
should make it trivial to port the fixes to the development branch (cd
ns-3-dev && hg pull ../ns-3.3 && hg merge).  It also makes it much more
difficult to make mistakes of committing unstable changes to the wrong
branch at the wrong time.

I mean the suggestion for future ns-3 versions; no need to destabilize the
ns-3.3 plan.

-- 
Gustavo J. A. M. Carneiro
INESC Porto, Telecommunications and Multimedia Unit
"The universe is always one step beyond logic." -- Frank Herbert