History log of /src/LOCKS (Results 51 – 57 of 57)
Revision Date Author Comments
# d97f4741 02-Jun-2005 Peter Wemm <peter@FreeBSD.org>

Document the previously existing RELENG_[45]_* security branch locks.

Approved by: core (quite a while ago)


# 072f68a7 02-Jun-2005 Peter Wemm <peter@FreeBSD.org>

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.

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

show more ...


# 8d958254 05-Jun-2008 Peter Wemm <peter@FreeBSD.org>

Update LOCKS syntax.

Approved by: core (implicit)


# 639c8983 24-Jan-2008 Colin Percival <cperciva@FreeBSD.org>

Once the release goes out, RELENG_7_* will need approval from so@.

Approved by: core (two months ago)


# a59bcb14 13-Jan-2006 Ruslan Ermilov <ru@FreeBSD.org>

Document commit constraints for RELENG_6_*.

Approved by: core (jhb)


# d97f4741 02-Jun-2005 Peter Wemm <peter@FreeBSD.org>

Document the previously existing RELENG_[45]_* security branch locks.

Approved by: core (quite a while ago)


# 072f68a7 02-Jun-2005 Peter Wemm <peter@FreeBSD.org>

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.

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

show more ...


123