> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/release/freebsd-5.4-release/5.4-errata-policy.md).

# FreeBSD 5.4 勘误处理策略

## 引言

以下是为 FreeBSD 5.4 应用勘误修复而提交请求的一般策略。

## 流程

勘误修复将由发行工程团队的某位成员应用，并与拥有该分支的安全官协调修复。还会发布勘误公告。如果多个勘误在大致相同的时间被处理，发行工程团队可以选择通过一份勘误公告一并处理多项勘误。

## 策略

### 勘误候选

勘误候选的判定标准是：那些严重破坏服务且没有已知规避方法的缺陷。例如，影响设备驱动程序预期功能的缺陷、可导致内核崩溃的缺陷等。

### 初始补丁

在初始阶段，勘误修复的处理方式应当与任何其他修复完全相同。它应当首先提交到 `HEAD`，并在那里经历正常的测试期。然后该修复应当照常进行 `MFC`。此时，如果你认为某项修复是勘误公告的候选，请联系发行工程团队，让他们知晓此事。

随后该修复应当在 `RELENG_5` 中停留一至两周。在此期间，请尽量让熟悉你所修改代码部分的另一位资深开发者审查该修复。你还应当从某个报告过该问题的人那里获得修复确实解决了问题的确认。假定在此测试期间未出现问题，那么就可以向 <re@FreeBSD.org> 发送正式请求。请附上需要应用于 5.4 的补丁以及审查过该修复的人员。

***

本文件及其他与发布相关的文档可从 [ftp://ftp.FreeBSD.org/](ftp://ftp.freebsd.org/) 下载。

如有关于 FreeBSD 的问题，请先阅读 [文档](http://www.freebsd.org/docs.html)，再联系 <questions@FreeBSD.org>。

如有关于此文档的问题，请发送电子邮件至 <doc@FreeBSD.org>。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://book.bsdcn.org/release/freebsd-5.4-release/5.4-errata-policy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.