【组件化架构--1.1.0】SDK版本号命名规范
简化版本
Google的太麻烦了，毕竟自己项目没那么大，有个简化的就好
- major-minor-bugfix-suffix
- alpha 接口不固定、功能实现中（开发中， 1.0.3-alpha）
- beta 接口固定、功能稳定（开发中， 1.0.3-beta）
- 无后缀 正式发行版本 （1.0.0）
Google Android版本
举例
1.0.0-alpha01
修个bug
1.0.1-alpha01
1.0.2-alpha02
1.0.2-beta01
1.0.2-rc01
1.0.2
名称
major-minor-bugfix-suffix
大版本-小版本-bugfix-后缀
1.0.1-beta02
Stable Release之前的三个阶段
通过后缀区分
Alpha
- API是不固定，可能会变更
- 功能可用，但 需求没有开发完
Beta
- 功能完成，但可能有bug
Release Candidate (RC) 待发行
- 稳定的release版本，可能改 几个关键的bug
Revision number
例如(01, 02），release之后再bugfix，在release的 重发版本号
原文
The libraries follow strict semantic versioning. A version string (like 1.0.1-beta02) contains three numbers representing major, minor, and bugfix levels. Pre-release versions also have a suffix that specifies the pre-release stage (alpha, beta, release candidate) and revision number (01, 02, and so on).
Every version of a library moves through three pre-release stages on its way to becoming a stable release. The criteria for each pre-release stage is:
Alpha
- Alpha releases are functionally stable, but may not be feature-complete.
- While a release is in alpha, APIs may be added, removed, or changed.
Beta
- Beta releases are functionally stable and have a feature-complete API surface.
They are ready for production use but may contain bugs. - A beta release cannot use experimental compiler features (such as @UseExperimental).
- Dependencies on other libraries must be beta, rc, or stable versions. No alpha dependencies are allowed.
Release Candidate (RC)
- A release candidate is a prospective stable release.
- It may contain critical last-minute fixes.
- Its API surface is final.
Dependencies on other libraries must be rc or stable versions only.
A library can have multiple versions at the same time. Each version has a different release stage. For example, while the stable release of androidx.activity could be 1.0.0, there might also be a 1.1.0-beta02 release as well as a 2.0.0-alpha01 release.
本文地址：https://blog.csdn.net/zhjali123/article/details/107597220