Re: Release process

["Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>]

On May 10,  4:03am, Felix Rosencrantz wrote:
} Subject: Release process
}
} Quiet time to me would be heavy restrictions on what can get checked
} in. I'd suggest things like no C code changes, unless they fix a
} crashing or other very serious bug.

This would be another reason to use a CVS branch.  Put the release code
on the branch; let people continue committing whatever they happen to be
working on, on the trunk; if it turns out to be a critical bug fix and
does not destabilize anything, selectively merge it to the branch.

On May 10, 12:33pm, Peter Stephenson wrote:
} Subject: Re: Release process
}
} That's fine.  It's been almost a year since the last full release anyway,
} and goodness knows how long since the first 3.0.

It'll be 5 years in August (June if you count pre-releases).

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net