Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Once the release goes out, RELENG_7_* will need approval from so@. | cperciva | 2008-01-24 | 1 | -0/+1 |
| | | | | Approved by: core (two months ago) | ||||
* | Document commit constraints for RELENG_6_*. | ru | 2006-01-13 | 1 | -0/+1 |
| | | | | Approved by: core (jhb) | ||||
* | Document the previously existing RELENG_[45]_* security branch locks. | peter | 2005-06-02 | 1 | -0/+3 |
| | | | | Approved by: core (quite a while ago) | ||||
* | Add a 'statement of intent' blurb to the top of MAINTAINERS. Split | peter | 2005-06-02 | 1 | -0/+8 |
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 |