finish release-process.md translation work

Author: node

translation/zh/patterns/release-process.md

@@ -8,53 +8,51 @@
 
 ## 问题
 
-When a team is deciding whether to use an InnerSource project, one of their considerations is whether they can rely on the given project for an extended period. Switching the tools/projects that they are using has a cost, so they only want to make those investments when necessary and has tangible benefits.
+当一个团队决定是否使用 InnerSource 项目时，他们的考虑因素之一是他们是否可以长期依赖于该项目。更换他们正在使用的工具/项目是有成本的，因此他们只希望在必要时进行这些投资，并获得切实的收益。
 
-It is common practice for Open Source projects to have versioned releases, with notes documenting breaking changes, and new features along with either a published binary or link to a Docker image. This practice may not be as transparent or well documented/visible for InnerSource projects, modules, etc.
+开源项目的通常做法是按版本发步，并在发行说明中记录破坏性变更和新功能，同时发布二进制文件或 Docker 镜像链接。对于 InnerSource 项目、模块等来说，这种做法可能不那么透明，或没有很好的文档化/可见性。
 
-InnerSource projects that don't have a published artifact or release process reduces trust. Teams won't know when they can expect the next release, when breaking changes are introduced, etc.
+没有发布制品或发布流程的 InnerSource 项目会降低信任度。团队不知道何时会发布下一个版本，何时会引入破坏性变更等。
 
 ## 上下文
 
-Large organizations produce a lot of internal software, much of which could be reused by teams across the company. Operational tooling, software libraries, and infrastructure as code (IaC) modules are common examples of this type of software. Most large organizations, however, don't publish internal software to be consumed by other teams in the company. This can occur either because they are to busy to provide documentation or don't realize the projects value to others.
+大型组织会生产大量的内部软件，其中很多软件都可以被整个公司的团队重复使用。运维工具、软件库和基础设施即代码（IaC）模块就是这类软件的常见例子。然而，大多数大型企业不会发布内部软件供公司其他团队使用。出现这种情况的原因可能是他们太忙，没有时间提供文档，或者没有意识到项目对其他人的价值。
 
-An internal or public source repository should be available where source code is stored, but teams lack a process for making software consumable by outside teams.
+应该有一个内部或公共代码库来存储源代码，但团队缺乏一个让外部团队使用软件的流程。
 
-As an organization grows and more internal software is written, the value of this pattern grows.
+随着组织的发展和更多内部软件的编写，这种模式的价值也在增加。
 
-## 约束
+## 约束 
 
-### 对于没有中心化 CI/CD 系统的组织来说很困难
+### 对于没有集中式 CI/CD 系统的组织来说很困难
 
-For organizations that don't provide engineers a centralized CI/CD system, automating a build and release process can be challenging. The team may need to stand up their own tool (Jenkins, Drone, etc). Without a CI/CD system, builds and release notes can still be produced, however, it may require a local build of the software and manual upload to whichever tool is hosting build artifacts.
+对于没有为工程师提供集中式 CI/CD 系统的组织而言，自动化构建和发布流程可能具有挑战性。团队可能需要建立自己的工具（Jenkins、Drone 等）。在没有 CI/CD 系统的情况下，仍然可以制作制品和发行说明，但可能需要在本地构建软件，并手动上传到托管制品的工具。
 
 ### 增加了发布发行说明的负担
 
-In addition to building your source code, writing release notes can be tedious without the ability to auto-generate a list of git commits. This would be left for someone to do manually, in addition to writing more high level details on a release.
+除了构建源代码之外，如果无法自动生成 git 提交列表，编写发行说明可能会很枯燥。除了编写更多发布细节之外，还需要其他人手动完成。
 
-### 没有位置来托管制品增加了难度
+### 没有地方来托管制品增加了难度
 
-If a company does not provide a centralized location for storing build artifacts (jars, npm modules, etc.) and docker images, engineers may be left deciding for themselves where is appropriate to store versioned software. Tools like GitHub provide this for you, however, if a company is not using one of these popular tools, this could pose a burden.
+如果公司没有提供一个集中位置来存储制品（jar、npm 模块等）和 docker 镜像，工程师可能需要自己决定在哪里适合存储各版本软件。 GitHub 等工具可以提供此功能，但是，如果公司不使用这些流行工具之一，这可能会造成负担。
 
 ## 解决方案
 
-By providing clear **release notes** and a published artifact you increase people's confidence that you are publishing a quality product that they can rely on.
+通过提供清晰的**发行说明**和已发布的制品，可以增强人们的信心，让他们相信你发布的是值得信赖的优质产品。。
 
-The following are key elements to achieve this:
+以下是实现这一目标的关键要素：
 
-- A CI/CD pipeline is located within your repository that [automates the release process](https://opensource.guide/best-practices/#use-tools-to-automate-basic-maintenance-tasks)
-- Build artifacts are generated by the CI/CD system (binary, docker image, jar, etc)
-- Releases are clearly labeled and tagged with [semantic versioning](https://github.com/semantic-release/semantic-release)
-- Releases include notes on New Features, Bug Fixes, and any "Breaking Changes"
+- 代码库中包含一个 CI/CD 流水线配置，可[自动化执行发布流程](https://opensource.guide/best-practices/#use-tools-to-automate-basic-maintenance-tasks)
+- 由 CI/CD 系统来生成制品（二进制、docker 镜像、jar 等等）
+- 发布的版本有清晰的标签，和[语义化的版本标记](https://github.com/semantic-release/semantic-release)
+- 发布内容包括新功能说明、错误修复和所有的“破坏性变更”。
 
-A good example of quality release notes can be found [here](https://github.com/jaegertracing/jaeger/releases).
+[这里](https://github.com/jaegertracing/jaeger/releases) 提供了一个高质量发行说明的范例。
 
 ## 结果背景
 
-Teams who come across your project will see published release notes and gain confidence in your tool. Published artifacts also make using your product easier and quicker to adopt. Having well-defined and visible processes such as these also help with cross-team collaboration and new contributors. Folks can be confident that their contributions are made available and distributed in a reasonable amount of time with a clear usage path.
-接触到您项目的团队会看到发布的发布说明，并对您的工具充满信心。发布的工件也会使您的产品使用起来更简单、更快捷。像这样定义明确、清晰可见的流程还有助于跨团队协作和新的贡献者。他们可以确信自己的贡献会在合理的时间内发布，并有明确的使用路径。
+接触到您项目的团队会看到已发布的发行说明，并对您的工具充满信心。已发布的制品也会使您的产品使用起来更简单、更快捷。像这样定义明确、清晰可见的流程还有助于跨团队协作和新的贡献者。他们可以确信自己的贡献会在合理的时间内发布，并有明确的使用路径。
 
-Release notes are also a great opportunity to [praise participants](praise-participants.md)! As we know, [documentation is extremely important](base-documentation.md) for new folks looking to get involved with your project. Praising outside teammates for contributions, including documentation and release notes, is a great way to foster community and grow your user base.
 发行说明也是[表扬参与者](raise-participants.md)的绝佳机会！众所周知，对于希望参与项目的新人来说，[文档是极其重要的](base-documentation.md)。表扬外部队友的贡献，包括文档和发布说明，是培养社区和扩大用户群的好方法。
 
 ## 已知实例
@@ -72,4 +70,4 @@ David Grizzanti
 
 ## 翻译校对
 
-* **2022-12-08** 翻译[Chris杨振涛](https:github.com/node)
+* **2022-12-08** 翻译 [Chris Yang](https:github.com/node)