Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA2094 ; Thu, 25 Feb 93 10:11:31 EST Xref: sserve comp.os.386bsd.questions:220 comp.os.386bsd.development:30 Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!mimsy!jds From: jds@cs.umd.edu (James da Silva) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.development Subject: Stabilizing 386bsd (was Re: WFJ's talk last night...) Message-ID: <64558@mimsy.umd.edu> Date: 24 Feb 93 16:28:36 GMT References: <1993Feb22.071916.14364@netcom.com> <C2vCxK.Evp@sugar.neosoft.com> <CGD.93Feb23140422@gaia.CS.Berkeley.EDU> Sender: news@mimsy.umd.edu Followup-To: comp.os.386bsd.development Organization: University of Maryland, Department of Computer Science Lines: 25 [Followups to the development group, please] cgd@gaia.CS.Berkeley.EDU (Chris G. Demetriou) writes: >peter@NeoSoft.com (Peter da Silva) writes: >=>I'd like to see the existing research platform stabilised to the point where >=>it can be used for research before playing with the documented interfaces. > >HEAR, HEAR! I agree. But, I would say don't fault Bill and Lynne for wanting to push forward rather than spend the rest of their days doing release management and regression testing. Rather, this is an ideal job for the wider 386bsd community to tackle. The Patchkit is a great start, and I gather it has the thumbs up from WFJ. It could form the basis for some sort of more ambitious "official unofficial" release tree. It's just a matter of resolving outstanding issues and getting everybody behind some mechanism for testing and approving patches and new subsystems. Jaime ............................................................................. : Stand on my shoulders, : jds@cs.umd.edu : James da Silva : not on my toes. : uunet!mimsy!jds : Systems Design & Analysis Group