[Ns-developers] ns-3.4 release plans

[Raj Bhattacharjea]

On Tue, Mar 3, 2009 at 8:53 AM, Tom Henderson <tomh at tomh.org> wrote:
> Raj Bhattacharjea wrote:
>
>>> From March 1st, release candidates will be released.  The bug count
>>> should
>>> ideally be zero during this time, and any remaining bugs discovered will
>>> be
>>> ironed out by the the 18th of March, when the final release of ns3.4 is
>>> made.
>>
>> I suggest we push this back to March 19.  We have adopted a policy of
>> consider P1 bugs as those which are broken behavior, and will be true
>> blockers which will hold up the _release candidates_;  that is, there
>> will be no P1 bugs in ns-3.4-RC1 (otherwise, how is it a candidate for
>> release?).  Any bugs found from beating on RC1 will be fixed and
>> posted as RC2, etc.
>
> Raj,
> I'm OK with slipping the release two weeks if it means that we will get all
> of the outstanding P1 bugs in your list fixed.  However, I think we should
> carefully consider whether additional bugs that come in will keep slipping
> the release further.  There is another option to slipping, which is to list
> open bugs as "known issues", and perhaps even to later do a small
> maintenance release.  So, I would suggest that we try not to slip the
> release further unless a major issue comes up that can't be fixed by April
> 1.

I like this idea.  We should triage bugs that keep coming in, and at
some point we'll have to draw a line and acknowledge that there are
known issues in the release, but make the release anyway, since we
can't hold up forever.  A maintenance release like ns-3.2.1 sounds
like a good idea.

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