[m-dev.] feature freeze
Peter Ross
petdr at cs.mu.OZ.AU
Fri Sep 4 09:20:22 AEST 1998
On 03-Sep-1998, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> Hi,
>
> In preparation for the next release, I suggest we instigate a freeze
> on adding new features. That means that we should not commit any changes
> which add new features. Bug fixes and the like are still allowed
> (and encouraged!), of course.
>
> I suppose it would be reasonable to make an exception for changes
> which have already reached the code review stage, and which do not
> look they pose much threat to the overall system stability.
> We might also want to make other exceptions if there are some
> particularly glaring omissions that could be easily rectified.
> But in general I would like people to discuss these things first,
> and to not commit any changes that add new features without
> getting general agreement.
>
> Comments welcome.
>
I think the next release should be delayed until we have the term
browser for the debugger done (not sure if this counts as a new feature).
Bert, any timeline for this?
Pete.
More information about the developers
mailing list