[Yocto RM]3 - Yocto Project Releases and the Stable Release Process

3 Yocto Project release and stable release process

Yocto Project The release process is predictable , Including primary and secondary （ spot ） edition . This short chapter provides information on how to name versions 、 Information about their life cycle and their stability .

3.1 Major and minor release rhythms

Yocto The project uses about every year 4 The month and 10 The main version is delivered at the six-month rhythm of the month （ for example 4.0.1）. Here are some of the main YP An example of this version , It also shows their codes . Information about codes used with major versions , see also “ Major version code ” part .

• 2.2（ Modi ）

• 2.1（ Kroggs ）

• 2.0（ Jethro ）

Although the rhythm is never perfect , But this timescale helps regular releases have powerful QA The version of the cycle , At the same time, users will not be overwhelmed by too many new editions . Rhythm is predictable , Many major holidays in different regions have been avoided .

Yocto The project is delivered from time to time （ spot ） edition , It is usually driven by the accumulation of sufficiently important fixes or enhancements to the relevant major version . Here are some examples of past releases ：

• 2.1.1

• 2.1.2

• 2.2.1

Point publishing represents a point in the main publishing Branch , It's complete QA The cycle and release process validate the content of the new branch .

Be careful ：
Realize that when patches are available , Patches can be merged into stable version branches .

3.2 Major version code

Each major version receives a code , Used to identify Yocto Project source repository