Documentation: process: Also mention Sasha Levin as stable tree maintainer

commit ba2457109d5b47a90fe565b39524f7225fc23e60 upstream.

Sasha has also maintaining stable branch in conjunction with Greg
since cb5d21946d ("MAINTAINERS: Add Sasha as a stable branch
maintainer"). Mention him in 2.Process.rst.

Cc: stable@vger.kernel.org
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Message-ID: <20251022034336.22839-1-bagasdotme@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
Bagas Sanjaya 2025-10-22 10:43:35 +07:00 committed by Greg Kroah-Hartman
parent 7d0a66e4bb
commit a68b06bdc1
1 changed files with 4 additions and 2 deletions

View File

@ -104,8 +104,10 @@ kernels go out with a handful of known regressions though, hopefully, none
of them are serious. of them are serious.
Once a stable release is made, its ongoing maintenance is passed off to the Once a stable release is made, its ongoing maintenance is passed off to the
"stable team," currently Greg Kroah-Hartman. The stable team will release "stable team," currently consists of Greg Kroah-Hartman and Sasha Levin. The
occasional updates to the stable release using the 5.x.y numbering scheme. stable team will release occasional updates to the stable release using the
5.x.y numbering scheme.
To be considered for an update release, a patch must (1) fix a significant To be considered for an update release, a patch must (1) fix a significant
bug, and (2) already be merged into the mainline for the next development bug, and (2) already be merged into the mainline for the next development
kernel. Kernels will typically receive stable updates for a little more kernel. Kernels will typically receive stable updates for a little more