From: Dante Strock <dantestrock@xxxxxxxxxxx>
As a possible suggestion, might it be worthwhile adding a terminology
section specific to each section of the kernel documentation? That way
developers have a handy reference to refer back to for terms they might
not understand.
---
Documentation/process/2.Process.rst:
- Changed some instances of 5.x to 6.x(though kept some instances of 5.x
that are used in examples).
- Clarified the term "rc" in brackets.
- Added a notice for people installing Git or Mercurial to check their
distribution repository for the latest version of the software.
Signed-off-by: Dante Strock <dantestrock@xxxxxxxxxxx>
---
Documentation/process/2.Process.rst | 26 +++++++++++++++-----------
1 file changed, 15 insertions(+), 11 deletions(-)
diff --git a/Documentation/process/2.Process.rst b/Documentation/process/2.Process.rst
index ef3b116492df..70f8a6603454 100644
--- a/Documentation/process/2.Process.rst
+++ b/Documentation/process/2.Process.rst
@@ -18,17 +18,17 @@ major kernel release happening every two or three months. The recent
release history looks like this:
====== =================
- 5.0 March 3, 2019
- 5.1 May 5, 2019
- 5.2 July 7, 2019
- 5.3 September 15, 2019
- 5.4 November 24, 2019
- 5.5 January 6, 2020
+ 6.10 July 14, 2024
+ 6.11 September 15, 2024
+ 6.12 November 17, 2024
+ 6.13 January 20, 2025
+ 6.14 March 24, 2025
+ 6.15 May 25, 2025
====== =================
-Every 5.x release is a major kernel release with new features, internal
+Every 6.x release is a major kernel release with new features, internal
API changes, and more. A typical release can contain about 13,000
-changesets with changes to several hundred thousand lines of code. 5.x is
+changesets with changes to several hundred thousand lines of code. 6.x is
the leading edge of Linux kernel development; the kernel uses a
rolling development model which is continually integrating major changes.
@@ -48,9 +48,9 @@ detail later on).
The merge window lasts for approximately two weeks. At the end of this
time, Linus Torvalds will declare that the window is closed and release the
-first of the "rc" kernels. For the kernel which is destined to be 5.6,
+first of the "rc"("release candidate") kernels. For the kernel which is destined to be 6.16,
for example, the release which happens at the end of the merge window will
-be called 5.6-rc1. The -rc1 release is the signal that the time to
+be called 6.16-rc1. The -rc1 release is the signal that the time to
merge new features has passed, and that the time to stabilize the next
kernel has begun.
@@ -99,7 +99,7 @@ release is made. In the real world, this kind of perfection is hard to
achieve; there are just too many variables in a project of this size.
There comes a point where delaying the final release just makes the problem
worse; the pile of changes waiting for the next merge window will grow
-larger, creating even more regressions the next time around. So most 5.x
+larger, creating even more regressions the next time around. So most 6.x
kernels go out with a handful of known regressions though, hopefully, none
of them are serious.
@@ -381,6 +381,10 @@ Some major subsystem maintainers use quilt to manage patches intended to go
upstream. For the management of certain kinds of trees (-mm, for example),
quilt is the best tool for the job.
+Note that not all Linux distributions have the latest version of Git
+or Mercurial available in their repositories. Consult the package
+maintainer for your distribution to get the package updated or
+download it directly from the website.
--
2.43.0
