diff --git a/en/release-notes/release-definitions/Release-version-definitions.md b/en/release-notes/release-definitions/Release-version-definitions.md index 07c9f9b80d4f4716a330bbc74c41518170e5a8a0..9205f0d6324e2db8f8f43f377bc9e1cc97f27c35 100644 --- a/en/release-notes/release-definitions/Release-version-definitions.md +++ b/en/release-notes/release-definitions/Release-version-definitions.md @@ -4,8 +4,6 @@ To ensure smooth version evolution and continuous stability and reliability of historical versions, the OpenHarmony community periodically pulls branches such as Long Term Support (LTS), Release, and Beta from Master and manages them based on the OpenHarmony lifecycle definition. -![1.png](figures/1.png) - ### Master @@ -13,11 +11,11 @@ Master is the main branch in the OpenHarmony community, to which code updates of ### LTS -LTS is a branch pulled from Master in the OpenHarmony community in the third quarter of each year. This branch is compiled, built, and tested in a centralized manner, and finally reviewed and released by the community. +LTS is a branch pulled from Master in the OpenHarmony community by year. This branch is compiled, built, and tested in a centralized manner, and finally reviewed and released by the community. ### Release -Release is a branch pulled from Master in the OpenHarmony community in the first quarter of each year. This branch is compiled, built, and tested in a centralized manner, and finally reviewed and released by the community. A Release branch has the same release requirements but a shorter maintenance period when compared with an LTS branch. +Release is a stable branch released in the OpenHarmony community. This branch is compiled, built, and tested in a centralized manner, and finally reviewed and released by the community. A Release branch has the same release requirements but a shorter maintenance period when compared with an LTS branch. ### Beta @@ -27,6 +25,16 @@ Beta is a branch pulled from Master in the OpenHarmony community irregularly. Th A tag version is a stable and reliable version created by applying patches to an LTS or a Release branch, with the purpose of fixing individual bugs, security vulnerabilities, and other necessary adaptation modifications. +### Commands for Downloading Branches + +| Branch | Download Command (repo + https) | Download Command (repo + ssh) | +| ------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | +| 1.0.1-Release | repo init -u https://gitee.com/openharmony/manifest -b OpenHarmony_1.0.1_release -m default.xml --no-repo-verify
repo sync -c
repo forall -c 'git lfs pull' | repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.1-Release -m default.xml --no-repo-verify
repo sync -c
repo forall -c 'git lfs pull' | +| 3.0-LTS | repo init -u https://gitee.com/openharmony/manifest.git -b OpenHarmony-3.0-LTS --no-repo-verify
repo sync -c
repo forall -c 'git lfs pull' | repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.0-LTS --no-repo-verify
repo sync -c
repo forall -c 'git lfs pull' | +| 3.1-Release | repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.1-Release -m default.xml --no-repo-verify
repo sync -c
repo forall -c 'git lfs pull' | repo init -u git@gitee.com:openharmony/manifest.git -b OpenHarmony-3.1-Release -m default.xml --no-repo-verify
repo sync -c
repo forall -c 'git lfs pull' | + + + ## Maintenance Policies ### Lifecycle Policies @@ -35,11 +43,11 @@ OpenHarmony provides lifecycle management services for LTS and Release branches #### Release -> Stop proactive maintenance -The Release SIG periodically makes and maintains tag version plans to resolve individual bugs, security vulnerabilities, and other major issues to ensure continuously stable and available branches. +​ The Release SIG periodically makes and maintains tag version plans to resolve individual bugs, security vulnerabilities, and other major issues to ensure continuously stable and available branches. #### Stop proactive maintenance -> Stop maintenance -The Release SIG no longer proactively plans and releases tag versions. It only fixes security vulnerabilities and major defects in corresponding branches. +​ The Release SIG no longer proactively plans and releases tag versions. It only fixes security vulnerabilities and major defects in corresponding branches. ### LTS and Release Maintenance Policies diff --git a/en/release-notes/release-definitions/mappings-between-label-and-system-versions.md b/en/release-notes/release-definitions/mappings-between-label-and-system-versions.md new file mode 100644 index 0000000000000000000000000000000000000000..85908177d389ca25620286af113a5a3aebc43a4a --- /dev/null +++ b/en/release-notes/release-definitions/mappings-between-label-and-system-versions.md @@ -0,0 +1,47 @@ +# Mappings Between Label Versions and System Versions + +A system version consists of the operating system name and software version number, separated by a hyphen (-). The software version number contains four digits, representing the major, minor, feature, and build versions in sequence. A system version can have a maximum of 64 characters (spaces not allowed) and can be obtained by running the API **GetOsFullName()**. + +The label versions released in the OpenHarmony community, for example, 1.1.x, 3.0.x, and 3.1.x, use 3-digit version numbers. To avoid troubles, the following table lists the mappings between the label versions released in the community and their system versions. + +## Mappings between label versions and system versions + +| Label Version | Small/Mini System Version | Standard System Version | Remarks | +| -------------------------- | -------------------- | -------------------- | -------------------------- | +| OpenHarmony_release_v1.1.0 | NA | NA | No system version is defined. | +| OpenHarmony-v1.1.1-LTS | NA | NA | No system version is defined. | +| OpenHarmony-v1.1.2-LTS | NA | NA | No system version is defined. | +| OpenHarmony-v1.1.3-LTS | NA | NA | No system version is defined. | +| OpenHarmony-v1.1.4-LTS | NA | NA | No system version is defined. | +| OpenHarmony-v1.1.5-LTS | NA | NA | No system version is defined. | +| OpenHarmony-v3.0-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | The **OsFullName** field is not modified.| +| OpenHarmony-v3.0.1-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | The **OsFullName** field is not modified.| +| OpenHarmony-v3.0.2-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | The **OsFullName** field is not modified.| +| OpenHarmony-v3.0.3-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | The **OsFullName** field is not modified.| +| OpenHarmony-v3.0.5-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | The **OsFullName** field is not modified.| +| OpenHarmony-v3.0.6-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | The **OsFullName** field is not modified.| +| OpenHarmony-v3.0.7-LTS | OpenHarmony-3.0.7.2 | OpenHarmony-3.0.7.2 | NA | +| OpenHarmony-v3.1-Release | OpenHarmony-1.0.1.0 | OpenHarmony-2.2.0.0 | The **OsFullName** field is not modified.| +| OpenHarmony-v3.1.1-Release | OpenHarmony-1.0.1.0 | OpenHarmony-2.2.0.0 | The **OsFullName** field is not modified.| +| OpenHarmony-v3.1.2-Release | OpenHarmony-1.0.1.0 | OpenHarmony-2.2.0.0 | The **OsFullName** field is not modified.| +| OpenHarmony-v3.1.3-Release | OpenHarmony-3.1.8.5 | OpenHarmony-2.2.0.0 | The **OsFullName** field is not modified.| +| OpenHarmony-v3.1.4-Release | OpenHarmony-3.1.9.6 | OpenHarmony-3.1.9.6 | NA | +| OpenHarmony-v3.1.5-Release | OpenHarmony-3.1.11.5 | OpenHarmony-3.1.11.5 | NA | + +## Changing System Versions + +### For 1.0.x, 3.0.x, and 3.1.x + +Integration configuration is unavailable for 1.0.x, 3.0.x, and 3.1.x in the community, so you need to modify the configuration in different files for small or mini systems and standard systems. + +For the small or mini system, the **OsFullName** field is in the following file: startup_syspara_lite/ frameworks / parameter / src / parameter_common.c + +For the standard system, the **OsFullName** field is in the following file: startup_syspara_lite/ interfaces / innerkits / native / syspara / src / sysversion.c + +Change the **static const int MAJOR_VERSION**, **static const int SENIOR_VERSION**, **static const int FEATURE_VERSION**, and **static const int BUILD_VERSION** fields to the corresponding system versions. + +### For 3.2.x and Later Versions + +Change the **const.ohos.fullname** field in the file **startup_init_lite/ services / etc_lite / param / ohos_const / ohos.para** + +to the corresponding system version. diff --git a/zh-cn/release-notes/release-definitions/Description of the relationship between label version and system version.md b/zh-cn/release-notes/release-definitions/mappings-between-label-and-system-versions.md similarity index 98% rename from zh-cn/release-notes/release-definitions/Description of the relationship between label version and system version.md rename to zh-cn/release-notes/release-definitions/mappings-between-label-and-system-versions.md index 17eef5442b46ad759bc584bc81aa2ea103caf438..3dfa8cf72c2df42abc3df3229177684ab17d8565 100644 --- a/zh-cn/release-notes/release-definitions/Description of the relationship between label version and system version.md +++ b/zh-cn/release-notes/release-definitions/mappings-between-label-and-system-versions.md @@ -1,47 +1,47 @@ -# 标签版本与系统版本对应对应关系说明 - -系统版本号指的是操作系统及其版本号，系统名与版本号之间以英文字符“-”连接，不能包含空格，最多64字符，随软件版本变更。其API接口名为GetOsFullName()。 - -OpenHarmony历史发布的1.1.x/3.0.x/3.1.x标签版本采用3位版本号命名，系统版本号采用4位命名，导致历史发布的版本所显示的系统版本号与标签版本号规则不统一。为避免造成困扰，我们对社区已发布的版本及其标签的对应关系整理成下表。 - -## 标签版本号与系统版本号对应关系 - -| 标签 | 小型/轻量系统版本号 | 标准系统版本号 | 备注 | -| -------------------------- | -------------------- | -------------------- | -------------------------- | -| OpenHarmony_release_v1.1.0 | NA | NA | 未定义系统版本号 | -| OpenHarmony-v1.1.1-LTS | NA | NA | 未定义系统版本号 | -| OpenHarmony-v1.1.2-LTS | NA | NA | 未定义系统版本号 | -| OpenHarmony-v1.1.3-LTS | NA | NA | 未定义系统版本号 | -| OpenHarmony-v1.1.4-LTS | NA | NA | 未定义系统版本号 | -| OpenHarmony-v1.1.5-LTS | NA | NA | 未定义系统版本号 | -| OpenHarmony-v3.0-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | 历史OSFullName字段未做修改 | -| OpenHarmony-v3.0.1-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | 历史OSFullName字段未做修改 | -| OpenHarmony-v3.0.2-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | 历史OSFullName字段未做修改 | -| OpenHarmony-v3.0.3-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | 历史OSFullName字段未做修改 | -| OpenHarmony-v3.0.5-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | 历史OSFullName字段未做修改 | -| OpenHarmony-v3.0.6-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | 历史OSFullName字段未做修改 | -| OpenHarmony-v3.0.7-LTS | OpenHarmony-3.0.7.2 | OpenHarmony-3.0.7.2 | NA | -| OpenHarmony-v3.1-Release | OpenHarmony-1.0.1.0 | OpenHarmony-2.2.0.0 | 历史OSFullName字段未做修改 | -| OpenHarmony-v3.1.1-Release | OpenHarmony-1.0.1.0 | OpenHarmony-2.2.0.0 | 历史OSFullName字段未做修改 | -| OpenHarmony-v3.1.2-Release | OpenHarmony-1.0.1.0 | OpenHarmony-2.2.0.0 | 历史OSFullName字段未做修改 | -| OpenHarmony-v3.1.3-Release | OpenHarmony-3.1.8.5 | OpenHarmony-2.2.0.0 | 历史OSFullName字段未做修改 | -| OpenHarmony-v3.1.4-Release | OpenHarmony-3.1.9.6 | OpenHarmony-3.1.9.6 | NA | -| OpenHarmony-v3.1.5-Release | OpenHarmony-3.1.11.5 | OpenHarmony-3.1.11.5 | NA | - -## 系统版本号修改方法 - -### 1.0.x/3.0.x/3.1.x版本修改方法 - -1.0.x/3.0.x/3.1.x版本上社区未做集成配置，小型/轻量系统和标准系统需要在不同文件上修改配置。 - -小型/轻量系统OsFullName修改文件路径：startup_syspara_lite/ frameworks / parameter / src / parameter_common.c - -标准系统OsFullName修改文件路径：startup_syspara_lite/ interfaces / innerkits / native / syspara / src / sysversion.c - -修改static const int MAJOR_VERSION、static const int SENIOR_VERSION、static const int FEATURE_VERSION、static const int BUILD_VERSION字段为对应系统版本号即可。 - -### 3.2.x及之后版本修改方法 - -3.2.x及之后版本修改文件路径： startup_init_lite/ services / etc_lite / param / ohos_const / ohos.para - +# 标签版本与系统版本对应对应关系说明 + +系统版本号指的是操作系统及其版本号，系统名与版本号之间以英文字符“-”连接，不能包含空格，最多64字符，随软件版本变更。其API接口名为GetOsFullName()。 + +OpenHarmony历史发布的1.1.x/3.0.x/3.1.x标签版本采用3位版本号命名，系统版本号采用4位命名，导致历史发布的版本所显示的系统版本号与标签版本号规则不统一。为避免造成困扰，我们对社区已发布的版本及其标签的对应关系整理成下表。 + +## 标签版本号与系统版本号对应关系 + +| 标签 | 小型/轻量系统版本号 | 标准系统版本号 | 备注 | +| -------------------------- | -------------------- | -------------------- | -------------------------- | +| OpenHarmony_release_v1.1.0 | NA | NA | 未定义系统版本号 | +| OpenHarmony-v1.1.1-LTS | NA | NA | 未定义系统版本号 | +| OpenHarmony-v1.1.2-LTS | NA | NA | 未定义系统版本号 | +| OpenHarmony-v1.1.3-LTS | NA | NA | 未定义系统版本号 | +| OpenHarmony-v1.1.4-LTS | NA | NA | 未定义系统版本号 | +| OpenHarmony-v1.1.5-LTS | NA | NA | 未定义系统版本号 | +| OpenHarmony-v3.0-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | 历史OSFullName字段未做修改 | +| OpenHarmony-v3.0.1-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | 历史OSFullName字段未做修改 | +| OpenHarmony-v3.0.2-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | 历史OSFullName字段未做修改 | +| OpenHarmony-v3.0.3-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | 历史OSFullName字段未做修改 | +| OpenHarmony-v3.0.5-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | 历史OSFullName字段未做修改 | +| OpenHarmony-v3.0.6-LTS | OpenHarmony-3.0.0.0 | OpenHarmony-3.0.0.0 | 历史OSFullName字段未做修改 | +| OpenHarmony-v3.0.7-LTS | OpenHarmony-3.0.7.2 | OpenHarmony-3.0.7.2 | NA | +| OpenHarmony-v3.1-Release | OpenHarmony-1.0.1.0 | OpenHarmony-2.2.0.0 | 历史OSFullName字段未做修改 | +| OpenHarmony-v3.1.1-Release | OpenHarmony-1.0.1.0 | OpenHarmony-2.2.0.0 | 历史OSFullName字段未做修改 | +| OpenHarmony-v3.1.2-Release | OpenHarmony-1.0.1.0 | OpenHarmony-2.2.0.0 | 历史OSFullName字段未做修改 | +| OpenHarmony-v3.1.3-Release | OpenHarmony-3.1.8.5 | OpenHarmony-2.2.0.0 | 历史OSFullName字段未做修改 | +| OpenHarmony-v3.1.4-Release | OpenHarmony-3.1.9.6 | OpenHarmony-3.1.9.6 | NA | +| OpenHarmony-v3.1.5-Release | OpenHarmony-3.1.11.5 | OpenHarmony-3.1.11.5 | NA | + +## 系统版本号修改方法 + +### 1.0.x/3.0.x/3.1.x版本修改方法 + +1.0.x/3.0.x/3.1.x版本上社区未做集成配置，小型/轻量系统和标准系统需要在不同文件上修改配置。 + +小型/轻量系统OsFullName修改文件路径：startup_syspara_lite/ frameworks / parameter / src / parameter_common.c + +标准系统OsFullName修改文件路径：startup_syspara_lite/ interfaces / innerkits / native / syspara / src / sysversion.c + +修改static const int MAJOR_VERSION、static const int SENIOR_VERSION、static const int FEATURE_VERSION、static const int BUILD_VERSION字段为对应系统版本号即可。 + +### 3.2.x及之后版本修改方法 + +3.2.x及之后版本修改文件路径： startup_init_lite/ services / etc_lite / param / ohos_const / ohos.para + 修改const.ohos.fullname字段为对应系统版本号即可。 \ No newline at end of file