Skip to contentSkip to conversation

Linux 2.6.11.1

DISCUSSION Shawn Starr 3 participants 4 messages Mar 5, 2005 – Mar 7, 2005

lore
Share & tools
lore
#0 lore raw

Sounds great, I can be a QA resource for what machines I have.

How do people get involved in QAing these releases?

What other help?

Shawn.

Quoted 35 lines
List:       linux-kernel
Subject:    Linux 2.6.11.1
From:       Greg KH <greg () kroah ! com>
Date:       2005-03-04 17:53:02
Message-ID: <20050304175302.GA29289 () kroah ! com>

[Download message RAW]

For those of you who haven't waded through the huge "RFD: Kernel release numbering" thread on lkml to realize that we are now going to start putting out 2.6.x.y releases, here's the summary:

A few of us $suckers will be trying to maintain a 2.6.x.y set of releases that happen after 2.6.x is released. It will contain only a set of bugfixes and security fixes that meet a strict set of guidelines, as defined by Linus at:
http://article.gmane.org/gmane.linux.kernel/283396

Chris Wright and I are going to start working on doing this work, we will have a <SOME_ALIAS>@kernel.org to post these types of bug fixes to, and a set of people we bounce the patches off of to test for "smells good" validation. We will also have a bk-commits type mailing list for those who want to watch the patches flow in, and a bk tree from which changsets can be pulled from.

Chris and I will be hashing all of the details out next Tuesday, and hopefully all the infrastructure will be in place soon. When that happens, we will post the full details on how all of this is going to work. In the meantime, feel free to CC: me and Chris on patches that everyone thinks should go into the 2.6.11.y releases.

But right now, Chris is on a plane, and we don't have the email alias set up, or the proper permissions set up on kernel.org to push changes into the v2.6 directory, but we have a few bugs that are needing to be fixed in the 2.6.11 release. And since our mantra is, "release early and often", here's the first release.

#1 lore raw
Quoted 3 lines · Shawn Starr

Sounds great, I can be a QA resource for what machines I have.

How do people get involved in QAing these releases?

Get the last release and test it out. If you have problems, and have simple/obvious patches, send them on.

thanks,

greg k-h

#2 lore raw

Sure, I can do this. Wrt to trivial patches, will these patches that go into rusty's patch bot go into Linus's tree or into the -mm tree?

The reason I ask that is because a trivial patch may fix an oops if there's an off-by-one problem and typically I'd submit that to the trivial patch bot.

That's why I was wondering about why this tree doesn't except trivial changes.

Thanks,
Shawn.

Quoted 11 lines · you
Quoted 3 lines · Shawn Starr

Sounds great, I can be a QA resource for what machines I have.

How do people get involved in QAing these releases?

Get the last release and test it out. If you have problems, and have simple/obvious patches, send them on.

thanks,

greg k-h

#3 lore raw
Quoted 3 lines · Shawn Starr

Sure, I can do this. Wrt to trivial patches, will these patches that go into rusty's patch bot go into Linus's tree or into the -mm tree?

The reason I ask that is because a trivial patch may fix an oops if there's an off-by-one problem and typically I'd submit that to the trivial patch bot.

No offense intended, but Rusty's trivial bot is often too slow for critical patches, so trivial-but-critical would be better off going to thru the x.y tree IMO.

Quoted 1 line

That's why I was wondering about why this tree doesn't except trivial changes.

It will if they fix real problems that people are experiencing.

The trivil bot and/or kernel-janitors paths for patches are better used for slow/non-critical patches, not patches that need quick attention and merging.

Quoted 14 lines

Thanks,
Shawn.

Quoted 8 lines · you
Quoted 3 lines · Shawn Starr

Sounds great, I can be a QA resource for what machines I have.

How do people get involved in QAing these releases?

Get the last release and test it out. If you have problems, and have simple/obvious patches, send them on.

Signature · 1 line
~Randy