1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@exmulti.com>) id 1QmEGW-0000dy-Ou
for bitcoin-development@lists.sourceforge.net;
Thu, 28 Jul 2011 00:15:52 +0000
X-ACL-Warn:
Received: from mail-iy0-f175.google.com ([209.85.210.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QmEGU-00033D-LD
for bitcoin-development@lists.sourceforge.net;
Thu, 28 Jul 2011 00:15:52 +0000
Received: by iyj12 with SMTP id 12so3211948iyj.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 27 Jul 2011 17:15:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.168.136 with SMTP id w8mr341591icy.267.1311812144953; Wed,
27 Jul 2011 17:15:44 -0700 (PDT)
Received: by 10.42.98.18 with HTTP; Wed, 27 Jul 2011 17:15:44 -0700 (PDT)
X-Originating-IP: [99.173.148.118]
In-Reply-To: <CABsx9T1667dxUj_iRtgbUR0ymBVOaADkGQU_CMF7z7e1-ctRcQ@mail.gmail.com>
References: <CABsx9T3W=n6VVJfOUqcd52oYvd-5hSwdOJudtVHK4g0bPGpXew@mail.gmail.com>
<1311765274.9830.3.camel@mei>
<CAJNQ0su9Qbi=zMaJA0G77UuHkXBy8k7YLBd4cec=Rc_-FGPBjA@mail.gmail.com>
<201107271028.28057.luke@dashjr.org>
<CAJ1JLtuuUUmrWGScbvYikAY_FOQhWpX5bt1NGp8VkpHk-hHOsQ@mail.gmail.com>
<1311786944.9830.77.camel@mei>
<CABsx9T1667dxUj_iRtgbUR0ymBVOaADkGQU_CMF7z7e1-ctRcQ@mail.gmail.com>
Date: Wed, 27 Jul 2011 20:15:44 -0400
Message-ID: <CA+8xBpcKNrGFKkN4mAW9E_s9Ph1=Qh9DNWryihDmD90HWMWF3Q@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QmEGU-00033D-LD
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Seeking advice: Encouraging bug-fixing
over new features
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 00:15:52 -0000
Linux kernel has not solved this problem; developers simply want to
work on interesting stuff, rather than debug, I think.
The best Linus has done so far it making certain periods of time
bugfix-only, refusing to take new feature pushes during the stability
period. If there are critical bugs, refusing to release the kernel
until a developer fixes the regressions they added.
Linux is large enough, though, that the ecosystem has grown a support
network, where companies pay for support (one big way my employer
stays in business), which includes bug fixes. So the paid support
orgs, like Red Hat, wind up going a lot of grunt work fixing because
they are the closest contact to actual users in the field encountering
problems with the Wonderful New Features bestowed upon them by
developers.
"drop and run" coding is a term for developers who appear, commit a
new feature, and then disappear without addressing bug reports or
other feedback regarding their contribution.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
|
