iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update blog.jade

This commit is contained in:
Rex 2016-09-15 11:10:03 +01:00 committed by GitHub
parent 3dec39ef78
commit 947dc0ecde
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
public/translate/cn/blog.jade
View File

@ -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: 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. the MAJOR version gets incremented when incompatible API changes are made to stable APIs,
1. 当对标为稳定的API进行不兼容的变更时，增加主版本号（MAJOR）， 1. 当对标为稳定的API进行不兼容的变更时，增加主版本号（MAJOR），