[m-dev.] code freeze on release branch

Fergus Henderson fjh at cs.mu.OZ.AU
Sat Nov 30 01:10:11 AEDT 2002

[I posted this in a thread on mercury-reviews, but I'm reposting
here for greater visibility.  In short I am proposing an even
stricter criteria for fixes on the release branch now: not just
any bug fix, only release-critical bug fixes.]

On 29-Nov-2002, Peter Ross <pro at missioncriticalit.com> wrote:
> This is one of many changes which fix problems with outputting floats.
> None of these changes are on the release branch, do we want to add all
> the changes to the release branch as well?

I think it is too late for changes like that now.
They are too likely to be destabilizing.
So I suggest we save these for 0.11.1 or 0.12.

I really want to release 0.11 soon.  I want the released version to
be passing all or very nearly all of its test cases on most platforms.
If we keep on making changes, this will never happen.  So at this point
I think bug fixes should go on the release branch only if they

	- address failures in the 0.11 test suite
	- are release-critical (e.g. those that break the build;
	  those that cause problems with installation or with
	  binary distributions; security holes;
	  or other serious problems like that)
	- are very simple (ideally a one-line change to a single file),
	  and are not likely to have much impact elsewhere,
	  and are important enough and low risk enough to be worth
	  risking delaying the release (e.g. the C# interface \n bug)

Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
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

More information about the developers mailing list