[Ns-developers] Socket API Addition for TCP Bug fixes
mazo at iitp.ru
Thu Oct 1 02:05:30 PDT 2009
> The following is really a generic comment not aimed at you or anyone in
> particular but I feel that this proposal is another example of our
> collective inability to merge new features/API early in our release
> cycles. I wonder if others share the same observation or if this is a
> figment of my naturally pessimistic imagination.
> A recurring event seems to be that new features are ignored early in the
> release cycle and everyone is rushing and pushing for new code just
> before the end of the release cycle. This leads to slippage in the
> release date (already twice in this cycle) and is making our job
> generally more painful than it should be by forcing us to work like
> madmen around the end of the cycle.
> More than this specific bug, I think that we need to address this more
> generic problem at some point. One solution could be to be really
> fascist about our release schedule and announce this early to make
> everyone aware that they can't get away with merging late. This means
> that every maintainer should take responsability for reviewing new
> features/patches timely. I don't know if this would fix the problem or
> if there is really a problem to be fixed but, well, I felt compelled to
> share my concerns publicly.
Well, I think it's not easy to change people's deadline scheduler in their minds.
Besides aggressively announcing release schedule, I propose to adapt the release schedule itself to changing needs if ns-3.
As ns-3 is growing larger and larger attracting more contributions (and maintainers review work), I suppose, it's worth enlarging "Late merge period" and "Maintenance phase" to at least 2 and 3 weeks respectively.
More information about the Ns-developers