Stable kernel release update
Subsystems (3)
v2 cover Stable kernel release update
The stable release process documented in stable-kernel-rules.rst needs to be updated to reflect current procedure.
Patch 1 and 2 reorganize section on submission procedure.
Patch 3 contains the actual process documentation update.
Patch 4 and 5 deals with various stable tree links.
Changes since v1 [1]:
- Following the submission: remove the case when manual backport is requested from the maintainer
- Review cycle: remove mention to [PATCH AUTOSEL/MANUALSEL]
- Review cycle: just spell "developers and testers" when testing -rc releases
- Review cycle: respond to -rc releases with Tested-by: message
- Submission procedure: split security patch note commit into its own patch
- Trees: add warning for stable-rc tree
[1]:
https://lore.kernel.org/linux-doc/[email protected]/T/#t
Bagas Sanjaya (5):
Documentation: add note block surrounding security patch note
Documentation: remove "For all other submissions..." section
Documentation: update stable review cycle documentation
Documentation: add link to stable release candidate tree
Documentation: update stable tree link
Documentation/process/stable-kernel-rules.rst | 35 ++++++++++++++----- 1 file changed, 27 insertions(+), 8 deletions(-)
base-commit: ffb217a13a2eaf6d5bd974fc83036a53ca69f1e2
Signature · 1 line
An old man doll... just what I always wanted! - Clara
PATCH v2 1/5 Documentation: add note block surrounding security patch note
Security patches have different handling than rest of patches for review.
Enclose note paragraph about such patches in .. note:: block.
--- Documentation/process/stable-kernel-rules.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
Documentation/process/stable-kernel-rules.rst +3 -1
@@ -35,7 +35,9 @@ Rules on what kind of patches are accepted, and which ones are not, into the Procedure for submitting patches to the -stable tree ---------------------------------------------------- - - Security patches should not be handled (solely) by the -stable review +.. note:: + + Security patches should not be handled (solely) by the -stable review process but should follow the procedures in :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>`.
Signature · 1 line
An old man doll... just what I always wanted! - Clara
PATCH v2 2/5 Documentation: remove "For all other submissions..." section
In reply to Bagas SanjayaRemove the redundant section, making option lists subsection of "Procedure for submitting patches..." section. As a replacement, begin the section by counting the options number, which is 3 options.
--- Documentation/process/stable-kernel-rules.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
Documentation/process/stable-kernel-rules.rst +1 -2
@@ -41,8 +41,7 @@ Procedure for submitting patches to the -stable tree process but should follow the procedures in :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>`. -For all other submissions, choose one of the following procedures ------------------------------------------------------------------ +There are three options: .. _option_1:
Signature · 1 line
An old man doll... just what I always wanted! - Clara
PATCH v2 3/5 Documentation: update stable review cycle documentation
In reply to Bagas SanjayaIn recent times, the review cycle for stable releases have been changed. In particular, there is release candidate phase between ACKing patches and new stable release. Also, in case of failed submissions (fail to apply to stable tree), manual backport (Option 3) have to be submitted instead.
Update the release cycle documentation on stable-kernel-rules.rst to reflect the above.
--- Documentation/process/stable-kernel-rules.rst | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-)
Documentation/process/stable-kernel-rules.rst +13 -4
@@ -82,8 +82,8 @@ it to be applied to. :ref:`option_2` and :ref:`option_3` are more useful if the patch isn't deemed worthy at the time it is applied to a public git tree (for instance, because it deserves more regression testing first). :ref:`option_3` is especially -useful if the patch needs some special handling to apply to an older kernel -(e.g., if API's have changed in the meantime). +useful if the original upstream patch needs to be backported (for example +the backport needs some special handling due to e.g. API changes). Note that for :ref:`option_3`, if the patch deviates from the original upstream patch (for example because it had to be backported) this must be very
@@ -152,8 +152,17 @@ Review cycle - If the patch is rejected by a member of the committee, or linux-kernel members object to the patch, bringing up issues that the maintainers and members did not realize, the patch will be dropped from the queue. - - At the end of the review cycle, the ACKed patches will be added to the - latest -stable release, and a new -stable release will happen. + - The ACKed patches will be posted again as part of release candidate (-rc) + to be tested by developers and testers. + - Usually only one -rc release is made, however if there are any outstanding + issues, some patches may be modified or dropped or additional patches may + be queued. Additional -rc releases are then released and tested until no + issues are found. + - Responding to the -rc releases can be done on the mailing list by sending + a "Tested-by:" email with any testing information desired. The "Tested-by:" + tags will be collected and added to the release commit. + - At the end of the review cycle, the new -stable release will be released + containing all the queued and tested patches. - Security patches will be accepted into the -stable tree directly from the security kernel team, and not go through the normal review cycle. Contact the kernel security team for more details on this procedure.
Signature · 1 line
An old man doll... just what I always wanted! - Clara
PATCH v2 4/5 Documentation: add link to stable release candidate tree
In reply to Bagas SanjayaThere is also stable release candidate tree. Mention it, however with a warning that the tree is for testing purposes.
--- Documentation/process/stable-kernel-rules.rst | 9 +++++++++ 1 file changed, 9 insertions(+)
Documentation/process/stable-kernel-rules.rst +9 -0
@@ -180,6 +180,15 @@ Trees https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git + - The release candidate of all stable kernel versions can be found at: + + https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/ + + .. warning:: + The -stable-rc tree is a snapshot in time of the stable-queue tree and + will change frequently, hence will be rebased often. It should only be + used for testing purposes (e.g. to be consumed by CI systems). + Review committee ----------------
Signature · 1 line
An old man doll... just what I always wanted! - Clara
PATCH v2 5/5 Documentation: update stable tree link
In reply to Bagas SanjayaThe link to stable tree is redirected to
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git. Update accordingly.
--- Documentation/process/stable-kernel-rules.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/process/stable-kernel-rules.rst +1 -1
@@ -178,7 +178,7 @@ Trees - The finalized and tagged releases of all stable kernels can be found in separate branches per version at: - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git + https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git - The release candidate of all stable kernel versions can be found at:
Signature · 1 line
An old man doll... just what I always wanted! - Clara