From: Jeff Garzik <jgarzik@exmulti.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Seeking advice: Encouraging bug-fixing over new features
Date: Wed, 27 Jul 2011 20:15:44 -0400 [thread overview]
Message-ID: <CA+8xBpcKNrGFKkN4mAW9E_s9Ph1=Qh9DNWryihDmD90HWMWF3Q@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T1667dxUj_iRtgbUR0ymBVOaADkGQU_CMF7z7e1-ctRcQ@mail.gmail.com>
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
next prev parent reply other threads:[~2011-07-28 0:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 1:31 [Bitcoin-development] Seeking advice: Encouraging bug-fixing over new features Gavin Andresen
2011-07-27 6:40 ` John Smith
2011-07-27 11:14 ` Joel Joonatan Kaartinen
2011-07-27 14:20 ` John Smith
2011-07-27 14:28 ` Luke-Jr
2011-07-27 14:42 ` Joel Joonatan Kaartinen
2011-07-27 14:53 ` John Smith
2011-07-27 16:02 ` Douglas Huff
2011-07-27 16:07 ` Rick Wesson
2011-07-27 16:47 ` Matt Corallo
2011-07-27 17:11 ` John Smith
2011-07-27 17:15 ` Joel Joonatan Kaartinen
2011-07-27 22:45 ` Gavin Andresen
2011-07-27 22:54 ` Joel Joonatan Kaartinen
2011-07-27 23:07 ` Matt Corallo
2011-07-28 6:31 ` John Smith
2011-07-28 0:15 ` Jeff Garzik [this message]
2011-07-28 15:37 ` Caleb James DeLisle
[not found] ` <1311811317.72375.YahooMailNeo@web121005.mail.ne1.yahoo.com>
2011-07-28 0:02 ` [Bitcoin-development] Fw: " Amir Taaki
2011-07-30 11:49 ` [Bitcoin-development] " Mike Hearn
2011-07-30 14:06 ` Rick Wesson
2011-07-30 14:07 ` Matt Corallo
2011-08-03 1:41 ` David Schwartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+8xBpcKNrGFKkN4mAW9E_s9Ph1=Qh9DNWryihDmD90HWMWF3Q@mail.gmail.com' \
--to=jgarzik@exmulti.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gavinandresen@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox