Date: Wed, 14 Mar 2001 21:39:02 +0000 From: Paul Richards <paul@freebsd-services.co.uk> To: obrien@FreeBSD.org Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: proposals for fixing the PROBLEM at hand Message-ID: <3AAFE4F6.9FAF6191@freebsd-services.co.uk> References: <20010312160321.B95497@mollari.cthul.hu> <200103130307.TAA41551@gndrsh.dnsmgr.net> <20010312193452.A2927@mollari.cthul.hu> <3AAE5A9A.341F634F@originative.co.uk> <20010314005648.I9369@klapaucius.zer0.org> <20010314011016.A28290@mollari.cthul.hu> <3AAF86A6.65492AEC@freebsd-services.co.uk> <3AAFB42F.95513604@gorean.org> <3AAFBED3.19D77C05@freebsd-services.co.uk> <20010314125115.B2341@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote: > > On Wed, Mar 14, 2001 at 06:56:19PM +0000, Paul Richards wrote: > > Which is why I've always advocated that there be a team of people that > > manages the -RELEASE branch and that it not be a free for all to > > committers. I'm happy that this be made up largely of the security team, > > they have the right sense of conservatism for this job but it does make > > sense for their remit to extend to system stability as well as security > > Not if they have neither the time or interest to do so. Are you > volunteering to be an _active_ part of the RELENG_4_3_0_RELEASE branch > team? Yes, if more help is needed to make RELENG_4_3_0_RELEASE work then I'm willing to provide it. > What about that bug that makes CAM work at 1/2 speed and the TCP stack at > 1/4 the performance. Would you consider these bugs that should be > committed to this branch? They certainly have no affect on the security > of the released system. No, since CAM at 1/2 speed and TCP stack at 1/4 performance were part of the feature set that existed when the production environment was commissioned. If my production environment is working fine based on those features then I'm not interested in any improvements since they might destabilise my working environment. My applications might actually rely on that poor performance, the last thing I'd want is for the behaviour of the underlying OS that my application runs on to change. > > > Perhaps what I consider to be a critical bug fix would always have > > fallen into their definition of security anyway since I'm really only > > talking about things that could cause data corruption or loss of > > service > > Yes, you haven't spelled this out clearly before. To me "maintenance mode" has always meant critical bug fixes only, I think that's a reasonably well understood definition in the industry. My point has been all along that -stable is not in maintenance mode but is being actively developed and we are therefore lacking a maintenance mode option for production environment users. The -RELEASE branch sounds like it will fill that gap but it's original remit of being security fixes only isn't exactly the same as maintenance fixes only. I'd be happy with the latter and would be willing to help support it. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AAFE4F6.9FAF6191>