Hi, According to fedora docs, fedora kernels are rebased against the mainline linux kernel periodically. I wanted to know that is there a way to figure out the rebase date for particular commits. Just looking at the git log, it just gives the same date as the date in the mainline linux kernel git log.
According to fedora docs, fedora kernels are rebased against the mainline linux kernel periodically. I wanted to know that is there a way to figure out the rebase date for particular commits. Just looking at the git log, it just gives the same date as the date in the mainline linux kernel git log.
rawhide rebases to linus's HEAD constantly during the weekdays. Once out of a merge window the RC that Linus usually does on a Sunday will be a nodebug build in rawhide on Monday.
A new stable, such as the just release 5.6 will usually start to land into stable Fedora releases around the .3 release in the stable release cycle, so I would expect the kernel team to start the process to get 5.6 ready for F-31 in the next week or so.
The "branched" release, in this case F-32, which is getting ready to go stable is a little more nuanced and is generally dependent on where the kernel/Fedora releases align, it's already on the 5.6.x series.
Peter
If i understood correctly. On a high level, you mean that the currently supported versions of fedora will be around less than a month behind the mainline linux kernel right? Best, - Ghani
On Mon, Apr 6, 2020 at 1:46 AM Peter Robinson pbrobinson@gmail.com wrote:
According to fedora docs, fedora kernels are rebased against the mainline linux kernel periodically. I wanted to know that is there a way to figure out the rebase date for particular commits. Just looking at the git log,
it
just gives the same date as the date in the mainline linux kernel git
log.
rawhide rebases to linus's HEAD constantly during the weekdays. Once out of a merge window the RC that Linus usually does on a Sunday will be a nodebug build in rawhide on Monday.
A new stable, such as the just release 5.6 will usually start to land into stable Fedora releases around the .3 release in the stable release cycle, so I would expect the kernel team to start the process to get 5.6 ready for F-31 in the next week or so.
The "branched" release, in this case F-32, which is getting ready to go stable is a little more nuanced and is generally dependent on where the kernel/Fedora releases align, it's already on the 5.6.x series.
Peter
On Mon, Apr 6, 2020 at 12:52 PM M. F. Ghani mfghani0@gmail.com wrote:
If i understood correctly. On a high level, you mean that the currently supported versions of fedora will be around less than a month behind the mainline linux kernel right?
They will be rebased to the latest stable release around a month after Linus tagged a new stable release. Rawhide is always up to date with the latest mainline development.
Best,
- Ghani
On Mon, Apr 6, 2020 at 1:46 AM Peter Robinson pbrobinson@gmail.com wrote:
According to fedora docs, fedora kernels are rebased against the mainline linux kernel periodically. I wanted to know that is there a way to figure out the rebase date for particular commits. Just looking at the git log, it just gives the same date as the date in the mainline linux kernel git log.
rawhide rebases to linus's HEAD constantly during the weekdays. Once out of a merge window the RC that Linus usually does on a Sunday will be a nodebug build in rawhide on Monday.
A new stable, such as the just release 5.6 will usually start to land into stable Fedora releases around the .3 release in the stable release cycle, so I would expect the kernel team to start the process to get 5.6 ready for F-31 in the next week or so.
The "branched" release, in this case F-32, which is getting ready to go stable is a little more nuanced and is generally dependent on where the kernel/Fedora releases align, it's already on the 5.6.x series.
Peter
On Mon, Apr 6, 2020 at 6:52 AM M. F. Ghani mfghani0@gmail.com wrote:
If i understood correctly. On a high level, you mean that the currently supported versions of fedora will be around less than a month behind the mainline linux kernel right?
Not exactly. It takes about a month for mainline .0 releases to filter down into stable Fedora releases. For example, 5.6.0 was released March 29th. We are running a Fedora test week on it next week, and if all goes well, I would expect 5.6.5 or so to land in Fedora 31 around April 21 or 22. Of course the mainline tree is already well into the merge window of 5.7. The average development cycle is 9-10 weeks, so at the point of the 5.7.0 release, Fedora 31 (and 32) will still be on 5.6.x. If I had to guess, we will rebase to 5.7.x for Fedora 31/32 around the end of June or early July. Rawhide moves on, and is never more than a day or 2 behind mainline.
Justin
kernel@lists.fedoraproject.org
-
Justin Forbes -
M. F. Ghani -
Peter Robinson