From 947dc0ecde3696b0e076c4b345860049df6c350d Mon Sep 17 00:00:00 2001 From: Rex Date: Thu, 15 Sep 2016 11:10:03 +0100 Subject: [PATCH] Update blog.jade --- public/translate/cn/blog.jade | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/public/translate/cn/blog.jade b/public/translate/cn/blog.jade index 387caee100..ce7ddc7d92 100644 --- a/public/translate/cn/blog.jade +++ b/public/translate/cn/blog.jade @@ -50,7 +50,7 @@ We heard loud and clear that our RC labeling was confusing. To make it easy to manage dependencies on stable Angular releases, starting today with Angular 2.0.0, we will move to semantic versioning. Angular versioning will then follow the MAJOR.MINOR.PATCH scheme as described by semver: - 我们听到很多人大声抱怨说我们的RC版本有些混乱。为了让您在Angular的稳定版中管理依赖更轻松，从今天的Angular 2.0.0开始，我们将迁移到“语义化版本”规范。今后的Angular版本将遵循semver所描述的MAJOR.MINOR.PATCH方案： + 我们明白RC版本标签有些扑朔迷离。为了让您在Angular的稳定版中管理依赖更轻松，从今天的Angular 2.0.0开始，我们将迁移到“语义化版本”规范。今后的Angular版本将遵循semver所描述的MAJOR.MINOR.PATCH方案： 1. the MAJOR version gets incremented when incompatible API changes are made to stable APIs, 1. 当对标为稳定的API进行不兼容的变更时，增加主版本号（MAJOR），