Re: [MAINTAINERS SUMMIT] [0/4] Common scenario for four proposals regarding regressions

Thorsten Leemhuis
2024-07-25T10:14:49Z

On 26.06.24 09:36, Greg KH wrote:
> On Tue, Jun 25, 2024 at 05:51:31PM -0400, Steven Rostedt wrote:
>> On Thu, 20 Jun 2024 12:02:21 -0400
>> James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
>>
>>> After all, given that stable is now delaying backports in the merge
>>> window, there should be at least a 2 week period where .0 is it
>>> (although it's also the two week period where we're not paying
>>> attention ...)
>>
>> I'm curious. Is there a stable branch that adds the stable patches in
>> continuously? That is, during the merge window, to have a branch that
>> adds the stable patches as they come in and then when the merge window
>> closes, to post the rc series with all the patches that have landed in
>> that branch?
>
> Yes, it's in the stable-queue git tree. And in the linux-stable-rc tree
> for those that can not consume quilt trees. Been there for years...

Out of curiosity, as I seem to be missing something here:

Steven afaics asked for "continuously […] during the merge window" and
the answer apparently made a few people (including myself) happy. But I
can't see anything like that. Were you just busy with other stuff this
merge window and didn't get around to pick up the changes, or did I look
at the wrong place?

I occasionally kept an eye on the trees you mentioned during in the past
few days and the branches/directories for 6.10.y in stable-queue and the
linux-stable-rc afaics have afaics been non existent until a few days
ago before you started to prepare 6.10.1 -- and since that one was
released ~20 hours ago those branches/directories do not contain any
additional changes.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/?h=linux-6.10.y
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/pending

I assume that will change over the next few days shortly before or after
the merge window -- at least that how I remember it from previous
cycles. But until then there is afaics no way to test the current stack
of changes that likely will end up in one of the next 6.10.y releases --
or is there and I just missed it somehow?

Ciao, Thorsten