On 6/9/25 12:17 PM, Dante Strock wrote:
[snip]
> 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.
>
> I do not object to these change and could apply this, but it might
> be nice at some point to rephrase this stuff so that we don't end up
> doing these updates repeatedly. After all, we'll be at 7.x within a
> year...
+1
> @@ -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,
>
> This is a separate change. But, of course, yesterday's 6.16-rc1 is
> in no way a "release candidate". It's really just the naming scheme
> that Linus uses for his testing releases, calling them "release
> candidates" muddies the water and risks reigniting old debates.
I have also thought of -rc as "release candidate", but -rc[1234] are
"early release candidates" to my brain. Or the could be called -nc[1234]
as in "non-candidates."
>
> +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.
>
[snip]
>
> Hello,
>
Parts of this email style guide might be helpful in the future:
https://people.kernel.org/tglx/notes-about-netiquette
[snip]
Thanks.
--
~Randy
