On Tue, Feb 20, 2001 at 10:58:47PM -0500, Jim Jagielski wrote:
> I'd also like to request that we *seriously* do a code freeze
> right now, so when we tag we are actually dealing with a known
> quantity. No more patches. No more commits. We freeze the code,
> test the snot out of it, and *then* t/r. These last minute
> patches are killing us :)
It's -well, uhm- rather simple to freeze the tree:
* create a "This tree is frozen until official release" script:
% cat >tree-is-frozen <<.
#!/bin/sh
echo "This tree is frozen, no more commits before release"
exit 1
.
* checkout CVSROOT
% cvs co CVSROOT
% cd CVSROOT
% mv ..../tree-is-frozen .
% chmod 755 tree-is-frozen
% cvs add tree-is-frozen
% echo >>checkoutlist tree-is-frozen
% cvs ci -m "Prepare script for freezing CVS trees" tree-is-frozen checkoutlist
* and freeze a specific cvs tree:
% echo "^apache-1.3/ /home/cvs/CVSROOT/tree-is-frozen" >>commitinfo
% cvs ci -m "Freeze apache-1.3 tree" commitinfo
* To thaw the tree again, remove the pattern "^apache-1.3/" from commitinfo
and re-commit
* The script could be enhanced (e.g., by adding invocation switches) to
a) check for the RM -- he should be able to commit
b) check for specific files (STATUS, CHANGES, Announcement)
About the "commitinfo" list:
# The "commitinfo" file is used to control pre-commit checks.
# The filter on the right is invoked with the repository and a list
# of files to check. A non-zero exit of the filter program will
# cause the commit to be aborted.
Would that help the RM's problems?
Martin
--
<[EMAIL PROTECTED]> | Fujitsu Siemens
<[EMAIL PROTECTED]> | 81730 Munich, Germany
