From ca5055d3098835ce9d95a8b6d6a950a48bb11b37 Mon Sep 17 00:00:00 2001 From: Thierry Reding Date: Mon, 12 Aug 2019 11:05:53 +0200 Subject: [PATCH] Describe the stable-queue release process Add a README file that describes how release candidates for stable kernels are created and how users are expected to use them. This is reworded from Greg's reply here: https://lore.kernel.org/stable/20190809085253.GA25046@kroah.com/ Link: https://lore.kernel.org/r/20190812090553.GA8903@ulmo Signed-off-by: Greg Kroah-Hartman --- README | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 README diff --git a/README b/README new file mode 100644 index 00000000000..868469a73f6 --- /dev/null +++ b/README @@ -0,0 +1,31 @@ +This repository is the canonical source for patches that make up the stable +kernel releases. It consists of a set of directories for each of the stable +kernels, as well as a directory that contains a snapshot of the patches for +each stable release. + +The patches for each release can be found along with a complete tarball of +a release in the following location: + + https://kernel.org/pub/linux/kernel/vX.Y/ + +For each stable release candidate, a patch representing the diff of all the +patches in the stable queue is uploaded here: + + https://kernel.org/pub/linux/kernel/vX.Y/stable-review/ + +As a convenience for people that want to test release candidates of stable +releases, a branch of the kernel git tree is created containing all of the +patches in the given stable queue. These branches are available in the +following repository: + + git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git + +A branch exists for each of the stable releases. Note, though, that these +branches are recreated from scratch by applying the queued stable patches +on top of the prior release. As a consequence, the branches are not fast- +forward and can change after a release candidate has been announced. The +contents of the branch may therefore not match exactly what was released +as the release candidate, depending on when you fetch it. No tags are +created to track individual release candidates. If you're interested in +exact reproducibility of a stable release candidate, please use the patches +from the location mentioned above. -- 2.47.3