diff options
| author | Chris Feyerchak <anonymous.contributor@example.org> | 2017-08-02 19:02:12 +0000 |
|---|---|---|
| committer | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2024-10-04 15:47:34 -0400 |
| commit | 6c59e1e5fe1e5f8dd2cb76be94951af11f00bf3d (patch) | |
| tree | e99a347619fc85d204b0dc4738d9262c30652a8f | |
| parent | 96c75872fac39c66b8cc3f16e19c06f4193cff0e (diff) | |
| download | backports-6c59e1e5fe1e5f8dd2cb76be94951af11f00bf3d.tar.gz | |
/* Backports development flow */ Edit for clarity
| -rw-r--r-- | wiki/Documentation_backports_hacking.mediawiki | 18 |
1 files changed, 6 insertions, 12 deletions
diff --git a/wiki/Documentation_backports_hacking.mediawiki b/wiki/Documentation_backports_hacking.mediawiki index 75c9a29..d98eea4 100644 --- a/wiki/Documentation_backports_hacking.mediawiki +++ b/wiki/Documentation_backports_hacking.mediawiki @@ -10,18 +10,12 @@ The project aims to optimize the backporting process by not only providing backp = Backports development flow = -The [https://git.kernel.org/cgit/linux/kernel/git/backports/backports.git backports.git] "master" -development branch always tracks "linux-next", allowing it to -track all the development trees. This ensures that at the end -of each merge window, the state of the backports will be -very close to the state of the first release candidate. At this -point, the backports project creates a further branch that tracks -the progress of the new release over the release candidate -evaluation period, to the major release, and on to its lifetime as -a stable kernel. - -The backports project thus makes three kinds -of backports releases possible: +# The [https://git.kernel.org/cgit/linux/kernel/git/backports/backports.git backports.git] "master" development branch always tracks "linux-next", allowing it to track all the development trees. +#* This ensures that, at the close of each merge window, the state of the backports will be very close to the state of the first release candidate. +# At the close of each merge window, the Backports Project creates a new branch. +#* This new branch tracks the progress of the impending release throughout the release candidate evaluation period, to the major release, and on to its lifetime as a stable kernel. + +The backports project thus makes three kinds of backports releases possible: * those derived from linux-next * those derived from the most recent release candidate (if any) |