Merge pull request #603 from coOps5566/release-2.0

翻译升级到最新版本

docs/source/upgrade.rst

@@ -1,47 +1,30 @@
-Upgrading to the latest release
+升级到最新版本
 ===============================
 
-If you’re familiar with previous releases of Hyperledger Fabric, you’re aware
-that upgrading the nodes and channels to the latest version of Fabric is, at a
-high level, a four step process.
-
-1. Backup the ledger and MSPs.
-2. Upgrade the orderer binaries in a rolling fashion to the latest Fabric version.
-3. Upgrade the peer binaries in a rolling fashion to the latest Fabric version.
-4. Update the orderer system channel and any application channels to the latest
-   capability levels, where available. Note that some releases will have
-   capabilities in all groups while other releases may have few or even no new
-   capabilities at all.
-
-For more information about capabilities, check out :doc:`capabilities_concept`.
-
-For a look at how these upgrade processes are accomplished, please consult these
-tutorials:
-
-1. :doc:`upgrading_your_components`. Components should be upgraded to the latest
-   version before updating any capabilities.
-2. :doc:`updating_capabilities`. Completed after updating the versions of all nodes.
-3. :doc:`enable_cc_lifecycle`. Necessary to add organization specific endorsement
-   policies central to the new chaincode lifecycle for Fabric v2.0.
-
-As the upgrading of nodes and increasing the capability levels of channels is by
-now considered a standard Fabric process, we will not show the specific commands
-for upgrading to the newest release. Similarly, there is no script in the ``fabric-samples``
-repo that will upgrade a sample network from the previous release to this one,
-as there has been for previous releases.
-
-.. note:: It is a best practice to upgrade your SDK to the latest version as a
-          part of a general upgrade of your network. While the SDK will always
-          be compatible with equivalent releases of Fabric and lower, it might
-          be necessary to upgrade to the latest SDK to leverage the latest Fabric
-          features. Consult the documentation of the Fabric SDK you are using
-          for information about how to upgrade.
+如果你熟悉 Hyperledger Fabric 以前的版本，那么你会知道，将节点和通道升级到 Fabric 的最新版本，从较高的角度看，有四步。
+
+1. 备份账本和 MSP。
+2. 以滚动的方式将 orderer 二进制文件升级到最新的 Fabric 版本。
+3. 以滚动方式将 peer 二进制文件升级到最新的 Fabric 版本。
+4. 在可用的情况下，将 orderer 系统通道和所有应用通道更新到最新功能级别。需要注意，某些版本将在所有组中具有功能，而其他版本可能几乎没有甚至根本没有新功能。
+
+有关功能的更多信息，请查看 :doc:`通道功能` 。
+
+有关如何完成这些升级的信息，请查询这些教程：
+
+1. :doc:`升级你的组件` 。在更新任何功能之前，应将组件升级到最新版本。
+2. :doc:`升级通道的功能级别` 。更新所有节点的版本后完成。
+3. :doc:`启用新的链码生命周期` 。有必要添加特定组织的背书策略，这对于 Fabric v2.0 的新链码生命周期至关重要。
+
+由于现在节点升级和提高通道的功能级别是 Fabric 的标准过程，因此我们将不展示升级到最新版本的具体命令。同样，``fabric-samples`` 仓库中也没有脚本像以前的版本一样将示例网络从以前的版本升级到该版本。
+
+.. note:: 最佳做法是将 SDK 升级到最新版本，这是网络常规升级的一部分。 虽然该 SDK 始终与相应版本的 Fabric 和更低的版本兼容，但可能有必要升级到最新的 SDK 以利用最新的 Fabric 功能。 有关如何升级的信息，请查阅所用 Fabric SDK 的文档。
 
 .. toctree::
    :maxdepth: 1
-   :caption: Upgrading to the latest release
+   :caption: 升级到最新版本
 
-   upgrade_to_newest_version
-   upgrading_your_components
-   updating_capabilities
-   enable_cc_lifecycle
+   升级到v2.0的注意事项
+   升级你的组件
+   升级功能级别
+   启用新的链码生命周期