Commit Graph

7 Commits

Author SHA1 Message Date
trasz
7b561089b2 Explicitly require Security Officer's approval for kernel PRNG bits.
Note that there is ongoing discussion about approval requirement
for userland PRNG bits.

Reviewed by:	so (des)
Approved by:	core (jhb)
Approved by:	re (gjb)
2013-09-17 14:19:05 +00:00
peter
2164515de7 Test commit to make sure commit mail works after moving the server.
Approved by:	core (implicit)
2012-12-29 16:03:23 +00:00
peter
2bcece939a Update LOCKS syntax.
Approved by:	core (implicit)
2008-06-05 19:47:58 +00:00
cperciva
a73485f346 Once the release goes out, RELENG_7_* will need approval from so@.
Approved by:	core (two months ago)
2008-01-24 22:07:03 +00:00
ru
fbea6d7fd2 Document commit constraints for RELENG_6_*.
Approved by:	core (jhb)
2006-01-13 06:51:43 +00:00
peter
ee40a88614 Document the previously existing RELENG_[45]_* security branch locks.
Approved by:  core (quite a while ago)
2005-06-02 22:57:30 +00:00
peter
8d69c7eef3 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 21:28:33 +00:00