HardenedBSD/LOCKS

$FreeBSD$

This file documents formal review/approval requirements that have been
approved by core.

subsystem       login   expires  notes
--------------------------------------

Special cases:
src/*	RELENG_4_*	Requires Security Officer approval.
src/*	RELENG_5_*	Requires Security Officer approval.
Add a 'statement of intent' blurb to the top of MAINTAINERS. Split the role of MAINTAINERS into advisory and strict parts. Introduce a new LOCKS file to document enforced locked parts of the tree. Strict locks are only added with core approval and will generally have a renewal timeout. Clarify that the source tree is a community effort, not a place to stake out 'turf'. This will be refined as needed. With-core-hat-on: Yes 2005-06-02 23:28:33 +02:00			$FreeBSD$

			`This file documents formal review/approval requirements that have been`
			`approved by core.`

			`subsystem login expires notes`
			`--------------------------------------`

Document the previously existing RELENG_[45]_* security branch locks. Approved by: core (quite a while ago) 2005-06-03 00:57:30 +02:00			`Special cases:`
			`src/* RELENG_4_* Requires Security Officer approval.`
			`src/* RELENG_5_* Requires Security Officer approval.`