head	1.48;
access;
symbols;
locks; strict;
comment	@# @;


1.48
date	2008.03.05.18.15.04;	author kensmith;	state Exp;
branches;
next	1.47;

1.47
date	2008.01.28.17.29.02;	author kensmith;	state Exp;
branches;
next	1.46;

1.46
date	2008.01.16.23.33.20;	author kensmith;	state Exp;
branches;
next	1.45;

1.45
date	2007.11.27.14.14.47;	author kensmith;	state Exp;
branches;
next	1.44;

1.44
date	2007.11.25.06.30.25;	author kensmith;	state Exp;
branches;
next	1.43;

1.43
date	2007.11.19.05.29.10;	author kensmith;	state Exp;
branches;
next	1.42;

1.42
date	2007.10.12.02.42.59;	author kensmith;	state Exp;
branches;
next	1.41;

1.41
date	2007.10.11.06.11.40;	author kensmith;	state Exp;
branches;
next	1.40;

1.40
date	2007.06.19.00.09.26;	author kensmith;	state Exp;
branches;
next	1.39;

1.39
date	2007.01.22.16.09.44;	author kensmith;	state Exp;
branches;
next	1.38;

1.38
date	2006.11.18.20.06.15;	author kensmith;	state Exp;
branches;
next	1.37;

1.37
date	2006.11.15.17.27.25;	author kensmith;	state Exp;
branches;
next	1.36;

1.36
date	2006.09.10.03.05.29;	author kensmith;	state Exp;
branches;
next	1.35;

1.35
date	2006.05.31.06.45.44;	author scottl;	state Exp;
branches;
next	1.34;

1.34
date	2006.05.26.13.08.13;	author kensmith;	state Exp;
branches;
next	1.33;

1.33
date	2006.05.15.22.47.57;	author cperciva;	state Exp;
branches;
next	1.32;

1.32
date	2006.05.12.12.19.57;	author kensmith;	state Exp;
branches;
next	1.31;

1.31
date	2006.05.09.22.10.54;	author scottl;	state Exp;
branches;
next	1.30;

1.30
date	2006.04.22.23.14.46;	author hrs;	state Exp;
branches;
next	1.29;

1.29
date	2006.02.01.18.01.51;	author kensmith;	state Exp;
branches;
next	1.28;

1.28
date	2005.12.20.04.06.55;	author cperciva;	state Exp;
branches;
next	1.27;

1.27
date	2005.11.04.01.22.27;	author scottl;	state Exp;
branches;
next	1.26;

1.26
date	2005.10.24.13.29.14;	author kensmith;	state Exp;
branches;
next	1.25;

1.25
date	2005.07.13.05.21.08;	author scottl;	state Exp;
branches;
next	1.24;

1.24
date	2005.07.11.08.50.06;	author scottl;	state Exp;
branches;
next	1.23;

1.23
date	2005.06.14.21.56.00;	author scottl;	state Exp;
branches;
next	1.22;

1.22
date	2005.06.14.13.54.22;	author kuriyama;	state Exp;
branches;
next	1.21;

1.21
date	2005.06.13.18.45.15;	author kensmith;	state Exp;
branches;
next	1.20;

1.20
date	2005.06.02.22.59.50;	author peter;	state Exp;
branches;
next	1.19;

1.19
date	2005.06.02.22.50.25;	author peter;	state Exp;
branches;
next	1.18;

1.18
date	2005.06.02.21.34.18;	author peter;	state Exp;
branches;
next	1.17;

1.17
date	2005.05.23.20.12.52;	author kensmith;	state Exp;
branches;
next	1.16;

1.16
date	2005.04.03.08.47.58;	author kensmith;	state Exp;
branches;
next	1.15;

1.15
date	2005.03.03.05.29.49;	author kensmith;	state Exp;
branches;
next	1.14;

1.14
date	2005.02.01.13.41.15;	author kensmith;	state Exp;
branches;
next	1.13;

1.13
date	2004.12.18.00.49.25;	author kensmith;	state Exp;
branches;
next	1.12;

1.12
date	2004.12.13.22.34.57;	author kensmith;	state Exp;
branches;
next	1.11;

1.11
date	2004.11.07.17.09.20;	author scottl;	state Exp;
branches;
next	1.10;

1.10
date	2004.09.19.22.36.36;	author nectar;	state Exp;
branches;
next	1.9;

1.9
date	2004.09.04.00.22.04;	author kensmith;	state Exp;
branches;
next	1.8;

1.8
date	2004.08.19.07.26.57;	author scottl;	state Exp;
branches;
next	1.7;

1.7
date	2004.08.18.00.06.25;	author scottl;	state Exp;
branches;
next	1.6;

1.6
date	2004.08.17.00.02.55;	author scottl;	state Exp;
branches;
next	1.5;

1.5
date	2004.06.03.13.06.35;	author des;	state Exp;
branches;
next	1.4;

1.4
date	2004.04.22.15.38.27;	author scottl;	state Exp;
branches;
next	1.3;

1.3
date	2004.04.15.15.58.20;	author nectar;	state Exp;
branches;
next	1.2;

1.2
date	2004.04.07.12.35.05;	author scottl;	state Exp;
branches;
next	1.1;

1.1
date	2004.03.30.00.18.16;	author kuriyama;	state Exp;
branches;
next	;


desc
@@


1.48
log
@Turn RELENG_7_0 over to the Security Team.

Approved by:	core (implicit)
@
text
@# Configuration file for checking approvals.
#
# If you want to commit to specific module/branch defined in this file,
# you should get approval from appropriate party.
#
# This file is maintained by core@@FreeBSD.org.
#
# Format is tab separated.
# Use # as first character in a line for comment.
#
# You should satisfy all of lines which matching to modules and branches
# to commit.
#
# 1st column is regexp for module name.
# 2nd column is regexp for branch/tag name.
# 3rd column is regexp used with "Approved by:[\t ]*" line.
#
# $FreeBSD$
#
# Note: CVS has no real concept of HEAD, but we have magic to make this work.
#^src/		HEAD		re
# Note that the RELENG_6 entry must be terminated with a 
# '$' in order to not match on other substrings.
#^src/		RELENG_7$	re
#^src/		RELENG_6$	re
^src/		RELENG_7_0	(security-officer|so)
^src/		RELENG_6_[0-3]	(security-officer|so)
^src/		RELENG_5_[0-5]	(security-officer|so)
^src/		RELENG_4_[3-9]	(security-officer|so)
^src/		RELENG_4_1[01]	(security-officer|so)
^CVSROOT/avail		HEAD	core
^CVSROOT/approvers	HEAD	(core|re)
^CVSROOT/access		HEAD	core
^src/LOCKS		HEAD	core
@


1.47
log
@Turn RELENG_6_3 over to the Security Team.

Approved by:	core (implicit)
@
text
@a24 1
^src/		RELENG_7_0	re
d26 1
@


1.46
log
@Release the code freeze on RELENG_7 but re@@ requests it be considered
a "code slush".  No large sweeping changes until 7.0 is out please.
We want to minimize headaches people have merging in things that are
meant to be in 7.0-RELEASE.

Approved by:	core (implicit)
@
text
@d27 1
a27 2
^src/		RELENG_6_3	re
^src/		RELENG_6_[0-2]	(security-officer|so)
@


1.45
log
@Release code freeze on RELENG_6.

Approved by:	core (implicit)
@
text
@d24 1
a24 1
^src/		RELENG_7$	re
@


1.44
log
@Start off newly created RELENG_6_3 branch under code freeze.  Add
upcoming RELENG_7_0 branch while here.

Approved by:	core (implicit)
@
text
@d26 1
a26 1
^src/		RELENG_6$	re
@


1.43
log
@Begin code freeze for 6.3-RELEASE.

Approved by:	core (implicit)
@
text
@d25 1
d27 1
@


1.42
log
@Release code freeze on HEAD.

Approved by:	core (implicit)
@
text
@d25 1
a25 1
#^src/		RELENG_6$	re
@


1.41
log
@Add RELENG_7 as something that requires re@@ approval.

Approved by:	core (implicit)
@
text
@d21 1
a21 1
^src/		HEAD		re
@


1.40
log
@Begin code freeze for FreeBSD-7.0 release cycle.

Approved by:	core (implicit)
@
text
@d24 1
@


1.39
log
@Turn RELENG_6_2 over to so@@.

Approved by:	core (implicit)
@
text
@d21 1
a21 1
#^src/		HEAD		re
@


1.38
log
@Release RELENG_6 from code freeze.

Approved by:	core (implicit)
@
text
@d25 1
a25 2
^src/		RELENG_6_2	re
^src/		RELENG_6_[0-1]	(security-officer|so)
@


1.37
log
@Prepare for RELENG_6_2, it will begin life in code freeze requiring
re@@ approval.

Approved by:	core (implicit)
@
text
@d24 1
a24 1
^src/		RELENG_6$	re
@


1.36
log
@Require re@@ approval for commits to RELENG_6 as we start the 6.2-REL
release cycle...

Approved by:	core (implicit)
@
text
@d25 1
@


1.35
log
@Give ownership of the RELENG_5_5 branch to the security officer.

Approved by:	re
@
text
@d24 1
a24 1
#^src/		RELENG_6$	re
@


1.34
log
@Release RELENG_5 from code freeze.  Leave behind a commented-out
RELENG_6 entry for future use and minor tweak to warning in the
comment describing it.

Approved by:	core (implicit)
@
text
@a24 1
^src/		RELENG_5_5	re
d26 1
a26 1
^src/		RELENG_5_[0-4]	(security-officer|so)
@


1.33
log
@Claim ownership of RELENG_6_1.

Approved by:	re (scottl)
@
text
@d22 1
a22 1
# Note that the RELENG_5 and RELENG_6 entries must be terminated with a 
d24 1
a24 1
^src/		RELENG_5$	re
@


1.32
log
@Prepare for RELENG_5_5 to be under re@@ control.

Approved by:	core (implicit)
@
text
@d26 1
a26 2
^src/		RELENG_6_1	re
^src/		RELENG_6_0	(security-officer|so)
@


1.31
log
@Release RELENG_6

Approved by:	re
@
text
@d25 1
@


1.30
log
@re@@ approval needed for RELENG_6_1 commits.

Approved by:	re (implicitly)
@
text
@a23 1
^src/		RELENG_6$	re
@


1.29
log
@Turn on approval checks for RELENG_5/RELENG_6 to start code freeze
for the 5.5 and 6.1 release cycles.

Approved by:	core (implicit)
@
text
@d26 1
@


1.28
log
@Claim ownership of RELENG_6_0.

While I'm here, edit the comment about RELENG_5 to point out that
RELENG_6 also needs a '$' to prevent matching against RELENG_6_*.

Approved by:	re (scottl)
@
text
@d24 2
a25 2
#^src/		RELENG_6$	re
#^src/		RELENG_5$	re
@


1.27
log
@Remove the approveral line for RELENG_6.  RELENG_6_0 remains under freeze.

Approved by: core
@
text
@d22 3
a24 3
^src/		RELENG_6_0$	re
# Note that the RELENG_5 entry must be terminated with a '$' in order to not
# match on other substrings.
d26 1
@


1.26
log
@Require re@@ approval for RELENG_6_0 commits.

Noticed by:	imp, wilko, des
Approved by:	core (implicitly)
@
text
@a21 1
^src/		RELENG_6$	re
@


1.25
log
@Unfreeze HEAD

Approved by:	core
@
text
@d23 1
@


1.24
log
@Put RELENG_6 under re@@ control.

Approved by:	core (implicit)
@
text
@d21 1
a21 1
^src/		HEAD		re
@


1.23
log
@Modify a stale comment about HEAD branches.  Clarify a rule.

Approved by: core
@
text
@d22 1
@


1.22
log
@Remove trailing whitespace.

Approved by:	core (implicit)
Reported by:	ru
@
text
@d20 1
a20 4
# XXX
# Note that the HEAD entry does not work as expected and should not be used.
# It is left in for documentation purposes only!
# XXX
d29 1
a29 1
^CVSROOT/approvers	HEAD	core
@


1.21
log
@Set it up so commits to HEAD should require re@@ approval.

Approved by:	core (implicit, normal part of release processing)
@
text
@d24 1
a24 1
^src/		HEAD		re 
@


1.20
log
@Oops, this file is sensitive to trailing whitespace.

Approved by: core
@
text
@d24 1
a24 1
#^src/		HEAD		re 
@


1.19
log
@Uncomment lock related entries.  The script appears to work as I'd expect.
@
text
@d34 1
a34 1
^src/LOCKS		HEAD	core	
@


1.18
log
@List the files that are going to need an 'Approved-by: core' to commit to -
src/LOCKS, CVSROOT/approvers, CVSROOT/avail and CVSROOT/access.

This is pending checks that the scripts can be made to work as expected.
@
text
@d31 4
a34 4
#^CVSROOT/avail		HEAD	core
#^CVSROOT/approvers	HEAD	core
#^CVSROOT/access		HEAD	core
#^src/LOCKS		HEAD	core	
@


1.17
log
@Turn over RELENG_5_4 to the Security Officer.
@
text
@d31 4
@


1.16
log
@RELENG_5_4 commits require re@@ approval.  RELENG_5 now unfrozen but
we ask people be conservative with what goes in until 5.4 gets released
so that RELENG_5 can be used as a proving ground for fixes.
@
text
@d28 1
a28 2
^src/		RELENG_5_4	re
^src/		RELENG_5_[0123]	(security-officer|so)
@


1.15
log
@Start the code freeze for 5.4-REL.
@
text
@d27 2
a28 1
^src/		RELENG_5$	re
@


1.14
log
@Turn over RELENG_4_11 to so@@.
@
text
@d27 1
a27 1
#^src/		RELENG_5$	re
@


1.13
log
@Remove the restriction on commits to RELENG_4, though this branch is
headed towards being the same as the older release branches.  There
are no plans on further RELENG_4 based releases so other than finishing
up 4.11 and any Errata/Security fixes work there is no reason to do
any further commits here.
@
text
@d30 1
a30 2
^src/		RELENG_4_10	(security-officer|so)
^src/		RELENG_4_11	re
@


1.12
log
@Begin code freeze for 4.11 release - require re@@ approval for RELENG_4
commits.
@
text
@a28 1
^src/		RELENG_4$	re
@


1.11
log
@Release RELENG_5 and move RELENG_5_3 to the security officer.
@
text
@d29 1
@


1.10
log
@Correct RELENG_5 tag: due to the lack of an explicit anchor, it is
erroneously matching the 5.x security branches.
@
text
@d21 1
a21 1
# Note the the HEAD entry does not work as expected and should not be used.
d25 4
a28 3
^src/		RELENG_5$	re
^src/		RELENG_5_[012]	(security-officer|so)
^src/		RELENG_5_3	re
@


1.9
log
@Add a trailing "/" to the regexp for RELENG_5 to see if that's why
the approval checks aren't working quite right.
@
text
@d25 1
a25 1
^src/		RELENG_5	re
@


1.8
log
@Add RELENG_5 to the approvers list.
@
text
@d25 1
a25 1
^src		RELENG_5	re
@


1.7
log
@Unlock HEAD from needing approval.
@
text
@d25 1
@


1.6
log
@Lock down the HEAD branch.  All commits must have an 'approved by: re' line.
@
text
@d20 5
a24 1
^src/		HEAD		re
@


1.5
log
@so now owns RELENG_4_10.
while here, add a preemptive entry for RELENG_4_11.
@
text
@d20 1
@


1.4
log
@Unrestrict the RELENG_4 src/ branch
@
text
@d23 2
a24 1
^src/		RELENG_4_10	re
@


1.3
log
@Add a missing `$' to the RELENG_4 regexp to avoid erroneous matches.
@
text
@a23 1
^src/		RELENG_4$	re
@


1.2
log
@Start the FreeBSD 4.10 code freeze.  All commits to RELENG_4 must have
Release Engineering team (re) approval.
@
text
@d24 1
a24 1
^src/		RELENG_4	re
@


1.1
log
@Check whether this commit is approved by appropriate party or not in
specific modules/branches.

We hope this check reduces accidental commits to reserved branches
(such as security branches).

Reviewed by:	core
@
text
@d24 1
@

