Jeff Garzik [ARCHIVE] on Nostr: š Original date posted:2011-07-27 šļø Summary of this message: Developers ...
š
Original date posted:2011-07-27
šļø Summary of this message: Developers prefer working on interesting stuff rather than debugging, leading to "drop and run" coding. Linux kernel has periods of bugfix-only and paid support for bug fixes.
š Original message: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 at exmulti.com
šļø Summary of this message: Developers prefer working on interesting stuff rather than debugging, leading to "drop and run" coding. Linux kernel has periods of bugfix-only and paid support for bug fixes.
š Original message: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 at exmulti.com