infra/landau.one.git, branch ssemin/doc-process-updates

landau-linux: maintenance: Add maintainers repos and 2MR description

2026-07-07T08:23:47+00:00

The LANDAU-linux maintenance document doesn't provide an important information regarding the way the sub-LANDAU-Linux repositories are supposed to be maintained. Moreover it is uncertain of how these changes are supposed to be collected into a single LANDAU-Linux release. Let's fix that by adding the detailed description of both of these processes into the chapter 6 concerning the maintainers responsibilities. The text is equipped with a mermaid gitGraph diagram visualising the GIT-flow in that regard. Signed-off-by: Serge Semin

landau-linux: maintenance: Refactor and enhance release process chapter

2026-07-07T08:23:47+00:00

The chapter "5. LANDAU-Linux release process" is a bit lame. First of all it constantly refers to a fixed release version v7.0.y meanwhile the document implies an approach irrelevant to the version number. Secondly the stages are differently described in the sub-paragraphs. Meanwhile it can be done in the more structured way, like list of the steps, key stage parameters and key notes. Thirdly the stages lack the details regarding the commit creation and it' format. Finally the LTS version support is no different from the stable release. So the current chapter 6. can be easily merged into the paragraph 5.4. Well ideally this should have been done in a set of the incremental commits. But this would have taken too much effort seeing the changes are interdependent. So let's introduce it in a refactor-like commit. This doesn't change the gist of the release process, but extends the description with the missing details and makes the text looking more structured by the paragraphs style unification. Signed-off-by: Serge Semin

landau-linux: maintenance: Add more detailed IC in the example

2026-07-07T08:23:47+00:00

At this moment it just states 'The Linux kernel 7.0 is released'. For the better LANDAU-Linux release cycle understanding it would be good to provide more details what it means from the LANDAU project point of view. Signed-off-by: Serge Semin

landau-linux: maintenance: Fix incorrect Linux version in the example

2026-07-07T08:23:47+00:00

The text states that the initial condition is the Linux kernel 6.12 release. But the further example refers to the 7.0 version which is way newer release. Fix the statement to indicate the correct version - 7.0. Signed-off-by: Serge Semin

landau-linux: maintenance: Fix incomplete RC-version in the example

2026-07-07T08:23:47+00:00

LANDAU-Linux RC stage is indicated by the version of the format 'l-rcX'. Meanwhile the example lists them as just 'rcX', which is a bit misleading. Fix that by adding the 'l-' prefix to the versions in the chapter 7. Signed-off-by: Serge Semin

landau-linux: maintenance: Fix incorrect LANDAU-Linux release lag

2026-07-06T13:20:30+00:00

The text mentions that the LANDAU-Linux releases are always behind the Linux kernel release. It's true but the lag is in one _PATCHLEVEL_ cycle since LANDAU-Linux is based on the last released Linux kernel version past RC-cycle. Meanwhile _SUBLEVEL_ is the stable kernel update which might be release even not once per week. Let's fix that. Signed-off-by: Serge Semin

landau-linux: maintenance: Extend GIT-branches description

2026-07-06T13:03:38+00:00

First of all the GIT-branches life-cycle block-scheme doesn't provide any info regarding the "landau-next" branch even though it's presented in the list of the main GIT-branches. Secondly the RC-stages is also missing in the stages sheet. Thirdly there is no need in splitting up the Normal(stable) and LTS branches diagram since their basic support is the same. Let's fix all of that by extending the GIT-branches description with the details regarding the 'landau-next' GIT-branch and it' relation to 'landau-V.P.y'. Also provide some more insight about what 'support' basically means in the framework of the LANDAU release cycle. Signed-off-by: Serge Semin

landau-linux: maintenance: Clarify the branch/repo words usage

2026-07-06T10:34:38+00:00

The text mostly uses the branch and repo words in reference to the GIT versioning system. In order to reduce some level of uncertainty it's better to add the "GIT-" prefix to these words to signify that the messages particularly mean the GIT-branches and repositories. Also there is no direct translation of the "Branching strategy" term. Let's use a more correct wording in that case: "GIT-branch organization strategy." Signed-off-by: Serge Semin

landau-linux: maintenance: Add missing RC-stage version/tags description

2026-07-06T10:34:38+00:00

The RC-stage version and tags format description is missing in the chapter 2. Meanwhile they are utilized afterwords in the chapters with the detailed process description and in the examples. Let's add the "l-rcX" version and "v7.0.l-rcX" tags format to have a more comprehensive Chapter 2. "Releases versioning format". Signed-off-by: Serge Semin

landau-linux: maintenance: Add missing EOL to glossary

2026-07-06T10:34:38+00:00

Since the text below uses the EOL abbreviation let's add it to the glossary chapter. EOL means End-Of-Life - a final stage of the product life-cycle indicating the end of the product support by means of the produce owner. Signed-off-by: Serge Semin