The definition of each version of the product under development (beta, alpha, rc, release...)

 alpha:

                    Alpha is an internal beta version, generally not released to the outside world, there will be many bugs. Unless you are also a tester, it is not recommended to use it. It is the first of the Greek letters, indicating the most advanced version, alpha is α, beta is β, The alpha version is the beta version that is earlier than the beta version, which is generally the version for internal testing. beta:                  This version has been greatly improved compared to the alpha version, eliminating serious bugs, but there is still a defect that needs to be further eliminated after multiple tests. This stage of the version will always add new features.        RC: (Release Candidate)                   Candidate means candidate, and it is a candidate version when used in software. Release.Candidate. is the release candidate. The biggest difference from the Beta version is that new functions will always be added in the Beta stage, but almost no new functions will be added in the RC version, and the main focus is on debugging! The RC version is the closest to the official version that is finally released to users. The version that corrects the bugs after the release is the official version, which is the last beta version before the official version. GA: (general availability)             For example: Apache Struts 2 GA This is the first stable version of Apache Struts 2, GA means General Availability, which means that the official began to recommend widespread use. Release:
       










             This version means "final version". After a series of beta versions of the previous version, there will eventually be an official version, which is a version that is finally delivered to users. This version is also sometimes referred to as the Standard Edition. Normally, Release will not appear on the software cover as a word, but instead is a symbol (R).


build:

        Refers to unit testing or functional testing



Let me say a few words here. In the library of the Maven repository, in addition to the above version definitions, there is another definition:

    SnapShot , Release .

When to use Snapshot version?

        The jar in the dependency library is in the development stage and will be updated frequently. In this case, if Release is used, the version number will be frequently increased, resulting in the abuse of the version number.


        The stage classification of the version is a part of the knowledge version classification. The version can also be defined for a product according to object-oriented, business version, environment, etc. Version definition, sometimes a branching part of Versioning. I also slowly feel that there is something special in the version.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324774578&siteId=291194637