Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA1500 ; Tue, 23 Feb 93 14:44:47 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!howland.reston.ans.net!sol.ctr.columbia.edu!The-Star.honeywell.com!umn.edu!csus.edu!netcom.com!hasty From: hasty@netcom.com (Amancio Hasty Jr) Subject: Re: [386BSD] A few patchkit comments Message-ID: <1993Feb16.202707.16709@netcom.com> Organization: Netcom Online Communications Services (408-241-9760 login: guest) References: <1993Feb16.182649.28351@zip.eecs.umich.edu> Date: Tue, 16 Feb 1993 20:27:07 GMT Lines: 30 IMHO: i don't know how the patches are being tested... I suggest that a small group of individuals get together to test the patches as they are incorporated into the patchkit. I like the idea of a small core group to do the testing and the screening. This approach has worked succesfully with XFree86 and XS3. There are always installations that are more troublesome than others so try to incorporate those in the pre-release stages. try to invite key "gurus" to review the patches - this is called code walk-through and it can help to reduce the number of bad patches. Keep a list of the patches which have been reviewed. Not everybody wants to build a kernel so try to release a kernel that can accomodate as wide audience as possible. Enough preaching... Good Luck! Amancio -- This message brought to you by the letters X and S and the number 3 Amancio Hasty | Home: (415) 495-3046 | ftp-site depository of all my work: e-mail hasty@netcom.com | sunvis.rtpnc.epa.gov:/pub/386bsd/incoming