"Actually... no. Since the point of auditing code is that audits should be done primarily before releases, less bugfixes means either better auditing or more laziness/secretiveness. See OpenBSD - a prime example of good code auditing."
Look at the linux development and release "traditions". Release early and release often gets code and concepts out in the open fast. They have generally been tested to an extend. What I mean by this is that Linux does pre-Alpha, Alpha and Beta testing usually in public. As such, the majority of bugreports are for beta/alpha software that is in common use. Fixes for production stuff are much rarer, like the BSD's app-level software. Try finding bug-fixes for Bash!!! Its a piece of code used on my OSS *nix systems, is fully GPL'd, yet 2.05 went smoothly from alpha to beta (current) IIRC. Someone correct me if I'm wrong, I dont keep up to date with Debian as much as I should lol.
Look at the linux development and release "traditions". Release early and release often gets code and concepts out in the open fast. They have generally been tested to an extend. What I mean by this is that Linux does pre-Alpha, Alpha and Beta testing usually in public. As such, the majority of bugreports are for beta/alpha software that is in common use. Fixes for production stuff are much rarer, like the BSD's app-level software. Try finding bug-fixes for Bash!!! Its a piece of code used on my OSS *nix systems, is fully GPL'd, yet 2.05 went smoothly from alpha to beta (current) IIRC. Someone correct me if I'm wrong, I dont keep up to date with Debian as much as I should lol.
Comment