From: Zenghui Yu <zenghuiyu96@gmail.com>
To: corbet@lwn.net, gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Zenghui Yu <zenghuiyu96@gmail.com>
Subject: [PATCH v2] Documentation/process/howto: Update for 4.x -> 5.x versioning
Date: Sun, 24 Feb 2019 23:45:23 +0800 [thread overview]
Message-ID: <1551023123-5031-1-git-send-email-zenghuiyu96@gmail.com> (raw)
As linux-5.0 is coming up soon, the howto.rst document can be
updated for the new kernel version. Change all 4.x references
to 5.x now.
Signed-off-by: Zenghui Yu <zenghuiyu96@gmail.com>
---
Documentation/process/howto.rst | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/Documentation/process/howto.rst b/Documentation/process/howto.rst
index f16242b..19001e2 100644
--- a/Documentation/process/howto.rst
+++ b/Documentation/process/howto.rst
@@ -235,16 +235,16 @@ Linux kernel development process currently consists of a few different
main kernel "branches" and lots of different subsystem-specific kernel
branches. These different branches are:
- - main 4.x kernel tree
- - 4.x.y -stable kernel tree
+ - main 5.x kernel tree
+ - 5.x.y -stable kernel tree
- subsystem specific kernel trees and patches
- - the 4.x -next kernel tree for integration tests
+ - the 5.x -next kernel tree for integration tests
-4.x kernel tree
+5.x kernel tree
~~~~~~~~~~~~~~~
-4.x kernels are maintained by Linus Torvalds, and can be found on
-https://kernel.org in the pub/linux/kernel/v4.x/ directory. Its development
+5.x kernels are maintained by Linus Torvalds, and can be found on
+https://kernel.org in the pub/linux/kernel/v5.x/ directory. Its development
process is as follows:
- As soon as a new kernel is released a two weeks window is open,
@@ -277,21 +277,21 @@ mailing list about kernel releases:
released according to perceived bug status, not according to a
preconceived timeline."*
-4.x.y -stable kernel tree
+5.x.y -stable kernel tree
~~~~~~~~~~~~~~~~~~~~~~~~~
Kernels with 3-part versions are -stable kernels. They contain
relatively small and critical fixes for security problems or significant
-regressions discovered in a given 4.x kernel.
+regressions discovered in a given 5.x kernel.
This is the recommended branch for users who want the most recent stable
kernel and are not interested in helping test development/experimental
versions.
-If no 4.x.y kernel is available, then the highest numbered 4.x
+If no 5.x.y kernel is available, then the highest numbered 5.x
kernel is the current stable kernel.
-4.x.y are maintained by the "stable" team <stable@vger.kernel.org>, and
+5.x.y are maintained by the "stable" team <stable@vger.kernel.org>, and
are released as needs dictate. The normal release period is approximately
two weeks, but it can be longer if there are no pressing problems. A
security-related problem, instead, can cause a release to happen almost
@@ -326,10 +326,10 @@ revisions to it, and maintainers can mark patches as under review,
accepted, or rejected. Most of these patchwork sites are listed at
https://patchwork.kernel.org/.
-4.x -next kernel tree for integration tests
+5.x -next kernel tree for integration tests
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Before updates from subsystem trees are merged into the mainline 4.x
+Before updates from subsystem trees are merged into the mainline 5.x
tree, they need to be integration-tested. For this purpose, a special
testing repository exists into which virtually all subsystem trees are
pulled on an almost daily basis:
--
2.7.4
next reply other threads:[~2019-02-24 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 15:45 Zenghui Yu [this message]
2019-02-25 18:26 ` Jonathan Corbet
2019-02-26 17:08 ` Zenghui Yu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1551023123-5031-1-git-send-email-zenghuiyu96@gmail.com \
--to=zenghuiyu96@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®