Skip to content

Latest commit

 

History

History
37 lines (26 loc) · 1.89 KB

MAINTAINERS.md

File metadata and controls

37 lines (26 loc) · 1.89 KB

This document will document some of the processes that members of the documentation team should adhere to.

本文档将记录文档组成员应遵守的一些过程

Review Period（审核周期）

The two weeks preceding a scheduled release is considered the review period of the Guides. 预定发布之前的两周被视为指南的审核期。 It is only during this period that pull requests for the relevant milestone are to be merged in. 只有在这段时间内，对相关里程碑的请求才会被合并。

Before the review period starts, the previous version should be re-released with any updates. 在审查期开始之前，先前的版本应该随任何更新而重新发布。

Labels（标签）

  • infrastructure: This label refers to issues that involve writing code, rather than writing documentation.
  • infrastructure: 这个标签指的是渗透写代码的问题，而不是写文档。
  • help wanted: This label is for issues that are suitable for any interested contributor to work on.
  • help wanted: 此标签适用于适合任何感兴趣的贡献者工作的问题。

Milestones（里程碑）

  • Future: Any future work that has is not scheduled for the next release
  • Future：未来的任何未被安排用于下一个版本的工作
  • M.N: Work that is scheduled for the M.N (Major.Minor) release
  • M.N：计划用于M.N（Major.Minor）版本的工作

Pull Requests（拉取请求）

Before merging you should check the following: 在合并之前，您应该检查以下内容：

  • Milestone. If it's assigned to the Milestone of the next release, only merge during the review period.
  • 里程碑。如果它被分配到下一个版本的里程碑，则只在审查期间合并。
  • Assignee. If it's assigned to someone, get explicit authorization from them before merging.
  • 受让人。如果它被分配给某人，在合并之前从他们获得明确的授权。