[m-dev.] feature freeze

[Mark Brown]

On 01-Oct-2002, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> Hi,
> 
> In preparation for the next release, I'd like to get some stability
> on the main line of our CVS repository before we make a branch for
> the release.  So I propose that we start a feature freeze.
> That means only committing changes that fix bugs,
> not changes that add new features.

When are you proposing that the freeze starts?  I'd like to commit the
change I posted last week to add the 'pd' command to the declarative
debugger.  I'll do that soon unless there are any objections.

> The idea would be to keep the feature freeze in place for a couple of
> weeks or so.

Presumably we will split a release branch off from the main branch, as
we have done in previous releases.  If this is the case, do we really
need a freeze period that long?  I can see that it would be useful to
declare a moratorium on commits while the split takes place, just to
make sure that there is no confusion about which commits come before the
split and which come after, but this shouldn't really need to last
longer than a few days to a week.  After the split, the release branch
can have as much time as it needs to settle down.

My motivation for wanting a shorter freeze period is that I am currently
testing a fairly major improvement to the declarative debugger, and I
would like to commit it soon after the split takes place (provided the
tests pass, of course).  I'd prefer, if possible, not to have to wait an
extra couple of weeks or so for that to go ahead.

Cheers,
Mark.

--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------