patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 8 Packages Projects Releases Wiki Activity

doc: release: minor tweaks

Browse source 
Minor tweak about length of stabilization phase and the merge process.

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
Anas Nashif 2023-02-28 22:15:55 +00:00
parent 8c410123b3
commit 6f1c764a92
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/project/release_process.rst
View file

@ -26,8 +26,8 @@ The Zephyr release model was loosely based on the Linux kernel model:
changes such as bug fixes and documentation will be merged unless granted a
special exemption by the Technical Steering Committee.
- Development phase: all changes are accepted (subject to approval from the
respective maintainers).
- Development phase: all changes are considered and merged, subject to
approval from the respective maintainers.
- Stabilisation phase: the release manager creates a vN-rc1 tag and the tree
enters the stabilization phase
- CI sees the tag, builds and runs tests; Test teams analyse the report from the
@ -55,7 +55,7 @@ sufficiently stable (and which is accepted by the maintainers and the wide commu
merged into the mainline tree. The bulk of changes for a new development cycle
(and all of the major changes) will be merged during this time.
The development phase lasts for approximately two months. At the end of this time,
The development phase lasts for approximately three months. At the end of this time,
the release owner will declare that the development phase is over and releases the first
of the release candidates. For the codebase release which is destined to be
3.1.0, for example, the release which happens at the end of the development phase