A proposal; making 2.6.20 a bugfix only version.
Quoted 9 lines · Andreas Mohr
Quoted 6 lines · Jesper Juhl
Let me make one very clear statement first: -stabel is a GREAT think and it is working VERY well.
That being said, many of the fixes I see going into -stable are regression fixes. Maybe not the majority, but still, regression fixes going into -stable tells me that the kernel should have seen more testing/bugfixing before being declared a stable release.Nice theory, but of course I'm pretty sure that it wouldn't work
Agreed.
Quoted 3 lines
(as has been said numerous time before by other people).
You cannot do endless testing/bugfixing, it's a psychological issue.
Agreed.
Quoted 5 lines
If you do that, then you end up with -preXX (or worse, -preXXX) version numbers, which would cause too many people to wait and wait and wait with upgrading until "that next stable" kernel version finally becomes available.
IOW, your tester base erodes, awfully, and development progress stalls.
IMHO, the psycho-problem is that you cannot intertwine development and stable in the same cycle. In that respect, the 2.6 development cycle is a real flop, as it does not allow for focus.
And focus is needed to achieve stability.
Think catch22...
Thanks!
--
Al
Quoted 31 lines · On Thu, 9 Nov 2006 07:57:48 +0300 Al Boldi <[email protected]> wrote:
Quoted 9 lines · Andreas Mohr
Quoted 6 lines · Jesper Juhl
Let me make one very clear statement first: -stabel is a GREAT think and it is working VERY well.
That being said, many of the fixes I see going into -stable are regression fixes. Maybe not the majority, but still, regression fixes going into -stable tells me that the kernel should have seen more testing/bugfixing before being declared a stable release.Nice theory, but of course I'm pretty sure that it wouldn't work
Agreed.
Quoted 3 lines
(as has been said numerous time before by other people).
You cannot do endless testing/bugfixing, it's a psychological issue.
Agreed.
Quoted 5 lines
If you do that, then you end up with -preXX (or worse, -preXXX) version numbers, which would cause too many people to wait and wait and wait with upgrading until "that next stable" kernel version finally becomes available.
IOW, your tester base erodes, awfully, and development progress stalls.IMHO, the psycho-problem is that you cannot intertwine development and stable in the same cycle. In that respect, the 2.6 development cycle is a real flop, as it does not allow for focus.
And focus is needed to achieve stability.
Quoted 7 lines
Think catch22...
Thanks!
--
Al
There are bugfixes which are too big for stable or -rc releases, that are queued for 2.6.20. "Bugfix only" is a relative statement. Do you include, new hardware support, new security api's, performance fixes. It gets to be real hard to decide, because these are the changes that often cause regressions; often one major bug fix causes two minor bugs.
Interestingly, adding a new feature often causes no bugs in the rest of the code, but it does increase the possible bug surface so most of the problems related to feature X are bugs in feature X.
Signature · 1 line
Stephen Hemminger <[email protected]>
Quoted 38 lines · Stephen Hemminger
Quoted 37 lines · Al Boldi
Quoted 9 lines · Andreas Mohr
Quoted 6 lines · Jesper Juhl
Let me make one very clear statement first: -stabel is a GREAT think and it is working VERY well.
That being said, many of the fixes I see going into -stable are regression fixes. Maybe not the majority, but still, regression fixes going into -stable tells me that the kernel should have seen more testing/bugfixing before being declared a stable release.Nice theory, but of course I'm pretty sure that it wouldn't work
Agreed.
Quoted 3 lines
(as has been said numerous time before by other people).
You cannot do endless testing/bugfixing, it's a psychological issue.
Agreed.
Quoted 6 lines
If you do that, then you end up with -preXX (or worse, -preXXX) version numbers, which would cause too many people to wait and wait and wait with upgrading until "that next stable" kernel version finally becomes available.
IOW, your tester base erodes, awfully, and development progress stalls.IMHO, the psycho-problem is that you cannot intertwine development and stable in the same cycle. In that respect, the 2.6 development cycle is a real flop, as it does not allow for focus.
And focus is needed to achieve stability.
Think catch22...
Thanks!
Quoted 8 lines
Quoted 2 lines
--
AlThere are bugfixes which are too big for stable or -rc releases, that are queued for 2.6.20. "Bugfix only" is a relative statement. Do you include, new hardware support, new security api's, performance fixes. It gets to be real hard to decide, because these are the changes that often cause regressions; often one major bug fix causes two minor bugs.
That's exactly the point I'm trying to get across; the 2.6 dev model tries to be two cycles in one, dev and stable, which yields an awkward catch22 situation.
The only sane way forward in such a situation is to realize the mistake and return to the focused dev-only / stable-only model.
This would probably involve pushing the current 2.6 kernel into 2.8 and starting 2.9 as a dev-cycle only, once 2.8 has structurally stabilized.
Thanks!
--
Al
Quoted 1 line · Al Boldi
Stephen Hemminger wrote:
[...]
Quoted 10 lines
Quoted 5 lines
There are bugfixes which are too big for stable or -rc releases, that are queued for 2.6.20. "Bugfix only" is a relative statement. Do you include, new hardware support, new security api's, performance fixes. It gets to be real hard to decide, because these are the changes that often cause regressions; often one major bug fix causes two minor bugs.
That's exactly the point I'm trying to get across; the 2.6 dev model tries to be two cycles in one, dev and stable, which yields an awkward catch22 situation.
Quoted 6 lines
The only sane way forward in such a situation is to realize the mistake and return to the focused dev-only / stable-only model.
This would probably involve pushing the current 2.6 kernel into 2.8 and starting 2.9 as a dev-cycle only, once 2.8 has structurally stabilized.
That was not what I was arguing for in the initial mail at all. I think the 2.6 model works very well in general. All I was pushing for was a single cycle focused mainly on bug fixes once in a while.
Signature · 3 lines
Jesper Juhl <[email protected]> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html
Quoted 19 lines · Jesper Juhl
Quoted 1 line · Al Boldi
Stephen Hemminger wrote:
[...]
Quoted 16 lines
Quoted 1 line
There are bugfixes which are too big for stable or -rc releases,
that are
Quoted 1 line
queued for 2.6.20. "Bugfix only" is a relative statement. Do you
include,
Quoted 1 line
new hardware support, new security api's, performance fixes. It
gets to
Quoted 2 lines
be real hard to decide, because these are the changes that often cause regressions; often one major bug fix causes two minor bugs.
That's exactly the point I'm trying to get across; the 2.6 dev model tries to be two cycles in one, dev and stable, which yields an awkward catch22 situation.
The only sane way forward in such a situation is to realize the mistake and return to the focused dev-only / stable-only model.
Quoted 8 lines
Quoted 3 lines
This would probably involve pushing the current 2.6 kernel into 2.8 and starting 2.9 as a dev-cycle only, once 2.8 has structurally stabilized.
That was not what I was arguing for in the initial mail at all. I think the 2.6 model works very well in general. All I was pushing for was a single cycle focused mainly on bug fixes once in a while.
I like the current model fine. From a developer point of view:
* More branches means having to fix and retest a bug more places. Workload goes up geometrically with number of versions.
So most developers end up ignoring fixing more than 2 versions; anything more than -current and -stable are ignored.
* Holding off the tide of changes doesn't work. It just leads to massive integration headaches.
* Many bugs don't show up until kernel is run on wide range of hardware, but kernel doesn't get exposed to wide range of hardware and applications until after it is declared stable. It is a Catch-22. The current stability range of
-subtree ... -mm ... 2.6.X ... 2.6.X.Y... 2.6.vendor
works well for most people. The people it doesn't work for are trying to get something for nothing. They want stability and the latest kernel at the same time.
There are some things that do need working on:
* Old bugs die, the bugzilla database needs a 6mo prune out.
* Bugzilla.kernel.org is underutilized and is only a small sample of the real problems. Not sure if it is a training, user, behaviour issue or just that bugzilla is crap.
* Vendor bugs (that could be fixed) aren't forwarded to lkml or bugzilla
* LKML is an overloaded communication channel, do we need:
[email protected] ?
* Developers can't get (or afford to buy) the new hardware that causes a lot of the pain. Just look at the number of bug reports due to new flavors of motherboards, chipsets, etc. I spent 3mo on a bug that took one day to fix once I got the hardware.
Quoted 26 lines · On Fri, 10 Nov 2006 08:42:58 -0800 Stephen Hemminger wrote:
Quoted 25 lines · Jesper Juhl
Quoted 1 line · Al Boldi
Stephen Hemminger wrote:
[...]
Quoted 21 lines
Quoted 1 line
There are bugfixes which are too big for stable or -rc releases,
that are
Quoted 1 line
queued for 2.6.20. "Bugfix only" is a relative statement. Do you
include,
Quoted 1 line
new hardware support, new security api's, performance fixes. It
gets to
Quoted 2 lines
be real hard to decide, because these are the changes that often cause regressions; often one major bug fix causes two minor bugs.
That's exactly the point I'm trying to get across; the 2.6 dev model tries to
be two cycles in one, dev and stable, which yields an awkward catch22 situation.The only sane way forward in such a situation is to realize the mistake and
return to the focused dev-only / stable-only model.This would probably involve pushing the current 2.6 kernel into 2.8 and starting 2.9 as a dev-cycle only, once 2.8 has structurally stabilized.
Quoted 5 lines
Quoted 4 lines
That was not what I was arguing for in the initial mail at all. I think the 2.6 model works very well in general. All I was pushing for was a single cycle focused mainly on bug fixes once in a while.
I like the current model fine. From a developer point of view:
I don't think that it's great, but having even/odd stable/development is even worse.
But I agree with Jesper and Andrew's comments in general, that we do have stability problems and we have a lack of people who are working on bugs.
Quoted 15 lines
* More branches means having to fix and retest a bug more places. Workload goes up geometrically with number of versions.
So most developers end up ignoring fixing more than 2 versions; anything more than -current and -stable are ignored.
* Holding off the tide of changes doesn't work. It just leads to massive integration headaches.
* Many bugs don't show up until kernel is run on wide range of hardware, but kernel doesn't get exposed to wide range of hardware and applications until after it is declared stable. It is a Catch-22. The current stability range of
-subtree ... -mm ... 2.6.X ... 2.6.X.Y... 2.6.vendor
works well for most people. The people it doesn't work for are trying to get something for nothing. They want stability and the latest kernel at the same time.
Quoted 6 lines
There are some things that do need working on:
* Old bugs die, the bugzilla database needs a 6mo prune out.* Bugzilla.kernel.org is underutilized and is only a small sample of the real problems. Not sure if it is a training, user, behaviour issue or just that bugzilla is crap.
Behavior, ease of use vs. email.
Quoted 1 line
* Vendor bugs (that could be fixed) aren't forwarded to lkml or bugzilla
ack
Quoted 2 lines
* LKML is an overloaded communication channel, do we need:
[email protected] ?
Either that or lkml is/remains for bug reporting and we move development somewhere else. Or my [repeated] preference:
do development on specific mailing lists (although there would likely need to be a fallback list when it's not clear which mailing list should be used)
Quoted 4 lines
* Developers can't get (or afford to buy) the new hardware that causes a lot of the pain. Just look at the number of bug reports due to new flavors of motherboards, chipsets, etc. I spent 3mo on a bug that took one day to fix once I got the hardware.
Yep.
---
~Randy
Quoted 25 lines · Randy Dunlap
Quoted 24 lines · On Fri, 10 Nov 2006 08:42:58 -0800 Stephen Hemminger wrote:
Quoted 23 lines · Jesper Juhl
Quoted 1 line · Al Boldi
Stephen Hemminger wrote:
[...]
Quoted 18 lines
Quoted 8 lines
There are bugfixes which are too big for stable or -rc releases, that are queued for 2.6.20. "Bugfix only" is a relative statement.
Do you include, new hardware support, new security api's, performance fixes. It
gets to be real hard to decide, because these are the changes that often cause regressions; often one major bug fix causes two minor bugs.That's exactly the point I'm trying to get across; the 2.6 dev model tries to
be two cycles in one, dev and stable, which yields an awkward catch22 situation.The only sane way forward in such a situation is to realize the mistake and
return to the focused dev-only / stable-only model.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 3 lines
This would probably involve pushing the current 2.6 kernel into 2.8 and starting 2.9 as a dev-cycle only, once 2.8 has structurally stabilized.
That was not what I was arguing for in the initial mail at all. I think the 2.6 model works very well in general. All I was pushing for was a single cycle focused mainly on bug fixes once in a while.
Temporary focusing won't help much, as you are dealing with people, who cannot be turned on and off like machines.
Quoted 8 lines
Quoted 1 line
I like the current model fine. From a developer point of view:
I don't think that it's great, but having even/odd stable/development is even worse.
But I agree with Jesper and Andrew's comments in general, that we do have stability problems and we have a lack of people who are working on bugs.
The problem is not just simple bugs that surface, it's deeper than that. Deep structural problems is what plagues 2.6.
Only a focused model may deal with such problems.
Quoted 9 lines
Quoted 9 lines
* More branches means having to fix and retest a bug more places. Workload goes up geometrically with number of versions. So most developers end up ignoring fixing more than 2 versions; anything more than -current and -stable are ignored.
* Holding off the tide of changes doesn't work. It just leads to massive integration headaches.
* Many bugs don't show up until kernel is run on wide range of
hardware, but kernel doesn't get exposed to wide range of hardware and applications until after it is declared stable. It is a Catch-22.
No Catch-22 here. You just fix those to achieve stability.
It's when you start to flip-flop dev/stable/dev/stable/... that you get Catch-22, which inhibits stability.
Quoted 5 lines
Quoted 5 lines
The current stability range of
-subtree ... -mm ... 2.6.X ... 2.6.X.Y... 2.6.vendor
works well for most people. The people it doesn't work for are
trying to get something for nothing. They want stability and the latest kernel at the same time.
That's not the impression I got from Andrew's stats.
Quoted 8 lines
Quoted 6 lines
There are some things that do need working on:
* Old bugs die, the bugzilla database needs a 6mo prune out.* Bugzilla.kernel.org is underutilized and is only a small sample of
the real problems. Not sure if it is a training, user, behaviour issue or just that bugzilla is crap.Behavior, ease of use vs. email.
Go email. Maybe even automated.
Quoted 7 lines
Quoted 2 lines
* Vendor bugs (that could be fixed) aren't forwarded to lkml or
bugzillaack
Quoted 2 lines
* LKML is an overloaded communication channel, do we need:
[email protected] ?
No.
Quoted 6 lines
Either that or lkml is/remains for bug reporting and we move development somewhere else. Or my [repeated] preference:
do development on specific mailing lists (although there would likely need to be a fallback list when it's not clear which mailing list should be used)
Yes. Needs more thought, though.
Quoted 6 lines
Quoted 4 lines
* Developers can't get (or afford to buy) the new hardware that
causes a lot of the pain. Just look at the number of bug reports due to new flavors of motherboards, chipsets, etc. I spent 3mo on a bug that took one day to fix once I got the hardware.Yep.
Thanks!
--
Al
Quoted 6 lines
The problem is not just simple bugs that surface, it's deeper than that. Deep structural problems is what plagues 2.6.
Only a focused model may deal with such problems.
can you at least provide a list of such structural problems? In fact, why don't you collect them and mail them out (bi)weekly... that may already do wonders.
Look at what Adrian is doing with the regressions; although the response isn't 100% people DO pay attention to it.... so maybe if you post a "structural problems list" people will actually start working on things.. (and of course you can help too ;)
Quoted 5 lines · Arjan van de Ven
Quoted 4 lines
The problem is not just simple bugs that surface, it's deeper than that. Deep structural problems is what plagues 2.6.
Only a focused model may deal with such problems.
Quoted 7 lines
can you at least provide a list of such structural problems? In fact, why don't you collect them and mail them out (bi)weekly... that may already do wonders.
Look at what Adrian is doing with the regressions; although the response isn't 100% people DO pay attention to it.... so maybe if you post a "structural problems list" people will actually start working on things.. (and of course you can help too ;)
Ok, things like OOM, scheduling, and block-io.
net looks ok, although I would suggest a redesign for 3.0.
Thanks!
--
Al
Quoted 14 lines · On Sat, 11 Nov 2006 00:22:52 +0300 Al Boldi <[email protected]> wrote:
Quoted 5 lines · Arjan van de Ven
Quoted 4 lines
The problem is not just simple bugs that surface, it's deeper than that. Deep structural problems is what plagues 2.6.
Only a focused model may deal with such problems.
Quoted 7 lines
can you at least provide a list of such structural problems? In fact, why don't you collect them and mail them out (bi)weekly... that may already do wonders.
Look at what Adrian is doing with the regressions; although the response isn't 100% people DO pay attention to it.... so maybe if you post a "structural problems list" people will actually start working on things.. (and of course you can help too ;)
Quoted 1 line
Ok, things like OOM, scheduling, and block-io.
If you want stability don't change these. But if you think you have better heuristics propose them for discussion.
Quoted 2 lines
net looks ok, although I would suggest a redesign for 3.0.
Facts, no vague pronouncements please.
Signature · 1 line
Stephen Hemminger <[email protected]>
Quoted 15 lines · Stephen Hemminger
Quoted 14 lines · Al Boldi
Quoted 12 lines · Arjan van de Ven
Quoted 4 lines
The problem is not just simple bugs that surface, it's deeper than that. Deep structural problems is what plagues 2.6.
Only a focused model may deal with such problems.
can you at least provide a list of such structural problems? In fact, why don't you collect them and mail them out (bi)weekly... that may already do wonders.
Look at what Adrian is doing with the regressions; although the response isn't 100% people DO pay attention to it.... so maybe if you post a "structural problems list" people will actually start working on things.. (and of course you can help too ;)
Quoted 4 lines
Quoted 1 line
Ok, things like OOM, scheduling, and block-io.
If you want stability don't change these. But if you think you have better heuristics propose them for discussion.
I don't think there is a lack of heuristics, nor is there a lack of discussion. What is needed, is a realization of the problem.
IOW, respective tree-owners need to come to a realization of the state of their trees, problem or not. If it has a problem, that problem needs to be fixed or backed out of stable and moved into dev.
Quoted 3 lines
Quoted 1 line
net looks ok, although I would suggest a redesign for 3.0.
Facts, no vague pronouncements please.
I meant structural OSI compliance.
Thanks!
--
Al
Quoted 28 lines · On Sat, 11 Nov 2006 07:15:49 +0300 Al Boldi <[email protected]> wrote:
Quoted 15 lines · Stephen Hemminger
Quoted 14 lines · Al Boldi
Quoted 12 lines · Arjan van de Ven
Quoted 4 lines
The problem is not just simple bugs that surface, it's deeper than that. Deep structural problems is what plagues 2.6.
Only a focused model may deal with such problems.
can you at least provide a list of such structural problems? In fact, why don't you collect them and mail them out (bi)weekly... that may already do wonders.
Look at what Adrian is doing with the regressions; although the response isn't 100% people DO pay attention to it.... so maybe if you post a "structural problems list" people will actually start working on things.. (and of course you can help too ;)Quoted 4 lines
Quoted 1 line
Ok, things like OOM, scheduling, and block-io.
If you want stability don't change these. But if you think you have better heuristics propose them for discussion.
I don't think there is a lack of heuristics, nor is there a lack of discussion. What is needed, is a realization of the problem.
IOW, respective tree-owners need to come to a realization of the state of their trees, problem or not. If it has a problem, that problem needs to be fixed or backed out of stable and moved into dev.
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
net looks ok, although I would suggest a redesign for 3.0.
Facts, no vague pronouncements please.
I meant structural OSI compliance.
Read the book "Network Algorithmics"; it has a clear discussion of why building your stack like the protocol specification is a bad idea.
Quoted 1 line
From: Stephen Hemminger <[email protected]>
Date: Fri, 10 Nov 2006 21:09:17 -0800
Quoted 10 lines
Quoted 3 lines · On Sat, 11 Nov 2006 07:15:49 +0300 Al Boldi <[email protected]> wrote:
Quoted 1 line · Stephen Hemminger
Al Boldi <[email protected]> wrote:
I meant structural OSI compliance.
Read the book "Network Algorithmics"; it has a clear discussion of why building your stack like the protocol specification is a bad idea.
Even Van Jacobson can be quoted as saying (to the effect) that layering is how you design protocols, _NOT_ how you implement them.
Quoted 11 lines · David Miller
From: Stephen Hemminger <[email protected]>
Date: Fri, 10 Nov 2006 21:09:17 -0800Quoted 8 lines
On Sat, 11 Nov 2006 07:15:49 +0300
Quoted 4 lines · Al Boldi
Quoted 1 line · Stephen Hemminger
Al Boldi <[email protected]> wrote:
I meant structural OSI compliance.
Quoted 7 lines
Quoted 3 lines
Read the book "Network Algorithmics"; it has a clear discussion of why building your stack like the protocol specification is a bad idea.
Even Van Jacobson can be quoted as saying (to the effect) that layering is how you design protocols, _NOT_ how you implement them.
The problem is that you let the implementation surface into user-land.
Thanks!
--
Al
Quoted 6 lines · Al Boldi
I don't think there is a lack of heuristics, nor is there a lack of discussion. What is needed, is a realization of the problem.
IOW, respective tree-owners need to come to a realization of the state of their trees, problem or not. If it has a problem, that problem needs to be fixed or backed out of stable and moved into dev.
I keep trying to parse this, and it keeps coming up as "content-free".
For starters, you don't even have a useful definition of "has a problem". There's a whole *range* of definitions for that, and even skilled and respected members of the Linux kernel community can disagree about whether something is "a problem". For example, see the thread about a week ago about "Remove hotplug cpu crap from cpufreq".
If, given a *specific* feature with high wart quotient, we can't agree on whether it needs to be fixed or backed out, we're doomed to fail if we start handwaving about problems "in general". As a group, we suck at anything that isn't specific, like "Algorithm A is better than B for case XYZ".
Quoted 9 lines · [email protected] wrote:
Quoted 6 lines · Al Boldi
I don't think there is a lack of heuristics, nor is there a lack of discussion. What is needed, is a realization of the problem.
IOW, respective tree-owners need to come to a realization of the state of their trees, problem or not. If it has a problem, that problem needs to be fixed or backed out of stable and moved into dev.
I keep trying to parse this, and it keeps coming up as "content-free".
Think denial.
Quoted 11 lines
For starters, you don't even have a useful definition of "has a problem". There's a whole *range* of definitions for that, and even skilled and respected members of the Linux kernel community can disagree about whether something is "a problem". For example, see the thread about a week ago about "Remove hotplug cpu crap from cpufreq".
If, given a *specific* feature with high wart quotient, we can't agree on whether it needs to be fixed or backed out, we're doomed to fail if we start handwaving about problems "in general". As a group, we suck at anything that isn't specific, like "Algorithm A is better than B for case XYZ".
We don't need to agree whether A is better than B, the mere fact that we acknowledge the problem is the first step in finding a solution.
So, either fix it, or back out.
OTOH, if there is no problem, then I guess we have blue skies...
Thanks!
--
Al
Quoted 6 lines · Randy Dunlap
Either that or lkml is/remains for bug reporting and we move development somewhere else. Or my [repeated] preference:
do development on specific mailing lists (although there would likely need to be a fallback list when it's not clear which mailing list should be used)
I've been thinking about this too for a while now. There is something like half of the email volume which are (semi-)automated emails containing patches moving from a GIT tree to another. I think that moving this to some linux-dev or something like this would :
1) reduce the noise on LKML so that problem reports are better caught
2) reduce the global email volume because instead of sending all these emails to 10-20000 persons(?), only maybe a thousand will be subscribed.
3) reduce even more the latency between post and publication due to 2.
I don't know if others would be interested, in which case it would be wise to poll on the subject and include Matti and Davem to the discussion.
Regards,
Willy
Quoted 13 lines · On Saturday November 11, [email protected] wrote:
Quoted 6 lines · Randy Dunlap
Either that or lkml is/remains for bug reporting and we move development somewhere else. Or my [repeated] preference:
do development on specific mailing lists (although there would likely need to be a fallback list when it's not clear which mailing list should be used)
I've been thinking about this too for a while now. There is something like half of the email volume which are (semi-)automated emails containing patches moving from a GIT tree to another. I think that moving this to some linux-dev or something like this would :
Quoted 7 lines
1) reduce the noise on LKML so that problem reports are better caught
2) reduce the global email volume because instead of sending all these emails to 10-20000 persons(?), only maybe a thousand will be subscribed.
3) reduce even more the latency between post and publication due to 2.I don't know if others would be interested, in which case it would be wise to poll on the subject and include Matti and Davem to the discussion.
I personally don't think the volume on lkml is a particular problem. I have filters which pick out the items that might be of particular interest to me (matching on words like 'nfs' 'raid' 'md' in my case) and the rest goes in to a bucket that I glance at occasionally. When I do, I scan the subject lines and read the things that seem interesting at the time, and delete the rest unread.
I prefer this to splitting lkml into multiple lists because it makes it much easier for me to change my areas of interest from time to time. I don't have to go and subscribe to different lists, I just use a different pattern for matching (either in my brain or in my filter).
I suspect the main reason that I miss problem reports that are relevant to me is that people choose poor Subject: lines. e.g. when I scan the subjects of a thread I might see multiple threads all with
Subject: Re: 2.6.18-rc5-mm2
and I'll have no idea what they are really about, and I don't have
time to read them all. If reporters simple put
(nfs problem)
at the end of the subject (or whatever is appropriate) then it would be a LOT easier to avoid missing things (some people do do this. I see their bug reports promptly when relevant).
Fortunately akpm is very good at reading all of these and forwarding things as appropriate (thanks Andrew) but that shouldn't really be necessary. And that situation won't be improved by reducing traffic on any list or splitting up the list (there are already plenty of other lists around). It really requires people who submit bug reports to think about what they are doing, and make it easy for people to find their bug report.
I guess bugzilla encourages people to think about their bug report and tag it accordingly. In that sense bugzilla is good. I just hate using it - I have to use a web browser, and it feels like a closed, private discussion, which really isn't appropriate.
NeilBrown
bugzilla (was Re: A proposal; making 2.6.20 a bugfix only version.)
Hi!
Quoted 4 lines
I guess bugzilla encourages people to think about their bug report and tag it accordingly. In that sense bugzilla is good. I just hate using it - I have to use a web browser, and it feels like a closed, private discussion, which really isn't appropriate.
Novell bugzilla is crap, but kernel.org bugzilla works with email. Try replying to one of its mails.
It works like small mailing list for each bug, with archive on the web. Yes, it is _still_ too much web, but it is way better than others...
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Quoted 2 lines · Randy Dunlap
Quoted 2 lines
* LKML is an overloaded communication channel, do we need:
[email protected] ?
Not sure if LKML is overloaded - subject filtering etc. And people expect they will be Ccopied if they are, for example, maintainers.
It's not the list for everybody, though.
Quoted 6 lines
Either that or lkml is/remains for bug reporting and we move development somewhere else. Or my [repeated] preference:
do development on specific mailing lists (although there would likely need to be a fallback list when it's not clear which mailing list should be used)
I don't like this idea as implemented now - it's probably fine for subsystem maintainers but it's prohibitive for an occasional submitter.
But... specific lists would make sense if - and only if:
- they are always mirrored to something like LKML so one doesn't need to subscribe to every possible list (as they appear).
- they are open as LKML is (no specific subscription required to post)
This way one could discuss things with/on a specific list (subscribed by subsystem maintainers and other interested people) and everyone reading the general list (or more general?) would see it too.
We could have a hierarchy:
- specific lists like lmkl-usb-ohci
- more general lkml-usb
- lkml, seeing all mail
This way every mail sent to lkml-usb-ohci would be sent to lkml-usb, and lkml-usb would be copied to lkml as well (I imagine some duplicate elimination would be a plus).
Anyone could discuss ohci writing to lkml-usb-ohci, discuss general USB writing to lkml-usb etc. Anyone subscribed to any of the above lists would see the traffic they are interested in, without a need for constant subscribing.
I assume the lists would be hosted on one domain to make it easy to post and perhaps to enable it to work at all.
If some form of sender address verification/scoring was in use I think it would be smart to recognize all people subscribed to more general lists to be "known" for this purpose (i.e., people subscribed to lkml would be considered "subscribed" while posting to lkml-usb-ohci).
Having written all of the above I now like the idea so be prepared to fight me hard if you don't :-)
Perhaps I could even help implementing it in some unspecified so called "free time".
Signature · 1 line
Krzysztof Halasa
Quoted 2 lines · Stephen Hemminger
...
* Old bugs die, the bugzilla database needs a 6mo prune out.
That's not that much of a problem.
There is me and there are some other people who sometimes go through older bugs asking submitters whether the issue is still present in a recent kernel.
And if it is not or the submitter doesn't answer the bug gets closed a few weeks later.
The problem with this approach is what to do when the bug is still present - it's quite unfair to ask a submitter whether a bug is still present, but having no way to help the submitter if he confirms it's still present.
A positive example is e.g. sparc: davem doesn't use Bugzilla, but when I forward bugs to him from Bugzilla I know that there will be an answer.
But for other subsystems like e.g. ext3 I don't know about anyone who will answer every time I forward a bug that is still present in the latest kernel.
Quoted 3 lines
* Bugzilla.kernel.org is underutilized and is only a small sample of the real problems. Not sure if it is a training, user, behaviour issue or just that bugzilla is crap.
At least one positive thing about Bugzilla is that it shows how bad our bug handling is - bug reports noone took care of are visible...
Quoted 1 line
* Vendor bugs (that could be fixed) aren't forwarded to lkml or bugzilla
We do already get more bug reports than we can handle.
As an example, until recently people were spreading the fairy tale noone would test -rc kernels. So I started a list of reported regressions by people who did test the -rc kernels, and this shows that we are even far away from handling recent regressions within one or two weeks - and the situation with other bugs looks much worse.
Quoted 2 lines
* LKML is an overloaded communication channel, do we need:
[email protected] ?
The problem is not how to communicate bugs - the problem is who will look after the bugs.
As an example, Andrew is already doing a great job in forwarding bugs from Bugzilla and linux-kernel to maintainers. It's not that maintainers miss bugs because they don't see them.
Quoted 4 lines
* Developers can't get (or afford to buy) the new hardware that causes a lot of the pain. Just look at the number of bug reports due to new flavors of motherboards, chipsets, etc. I spent 3mo on a bug that took one day to fix once I got the hardware.
If only this was the only problem...
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed