Date: Sun, 8 Jun 2008 16:52:36 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Josh Carroll <josh.carroll@gmail.com> Cc: Adrian Chadd <adrian@freebsd.org>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: 6.2; 6.3; EOL; combustible discussions Message-ID: <20080608164928.L16871@fledge.watson.org> In-Reply-To: <8cb6106e0806071938x6a524ba4o969fbc4f0c85206@mail.gmail.com> References: <d763ac660806071917n5df49144r1b81ca0b7bee6d69@mail.gmail.com> <8cb6106e0806071938x6a524ba4o969fbc4f0c85206@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 7 Jun 2008, Josh Carroll wrote: > While it would be interesting to see the response here, it still doesn't > necessarily provide a solution. It will still involved developers' time to > QA the user-submitted patches, so it won't entirely eliminate the additional > workload for maintainers. There is also zero (enforceable) accountability. > If X people commit to this, what happens when only a fraction of them > actually do end up helping? Just to be clear here, Adrian's claim that if someone else provided patches for 6.2, they would be committed, is incorrect. The cost of committing the patch is almost zero -- the cost of QA'ing the patch, doing freebsd-update rebuilds, preparing security or errata notices, etc, is extremely real, and the reason that we carefully limit the number of releases we support at once. In fact, I'd argue that we have been supporting too many releases at once, as I think our latency for shipping errata notices and advisories is too high. By reducing the number of releases we support, we improve the speed and attention we can give each notice/advisory, which is an important consideration. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080608164928.L16871>