From owner-freebsd-current Wed Feb 28 09:30:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA24737 for current-outgoing; Wed, 28 Feb 1996 09:30:11 -0800 (PST) Received: from gw2.att.com (gw2.att.com [192.20.239.134]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA24693 for ; Wed, 28 Feb 1996 09:30:01 -0800 (PST) From: ejc@nasvr1.cb.att.com Received: from nasvr1.cb.att.com (naserver1.cb.att.com) by ig1.att.att.com id AA16199; Wed, 28 Feb 96 08:11:05 EST Received: by nasvr1.cb.att.com (5.x/EMS-1.1 Sol2) id AA27012; Wed, 28 Feb 1996 08:13:29 -0500 Cc: dob@nasvr1.cb.att.com Received: from ginger.cb.att.com by nasvr1.cb.att.com (5.x/EMS-1.1 Sol2) id AA27003; Wed, 28 Feb 1996 08:13:24 -0500 Received: by ginger.cb.att.com (5.x/EMS-1.1 Sol2) id AA14142; Wed, 28 Feb 1996 08:16:57 -0500 Date: Wed, 28 Feb 1996 08:16:57 -0500 Message-Id: <9602281316.AA14142@ginger.cb.att.com> To: freebsd-current@freebsd.org Subject: -current submitting policys Original-Cc: dob@nasvr1 X-Sun-Charset: US-ASCII Sender: owner-current@freebsd.org Precedence: bulk Hello I supped -current on 2-27-96, to bring my tree up to date. Building of libc failed in libc/db also libutil died because the Makefile had a '-C' not a '-c'. I have my -current build env chroot'ed so instabilities in -current won't bring down my whole system. This brings up a few questions at least for me. Should the code be buildable and installable on the developers machine with the latest -current before submitting? Should a code diff be inspected by another peer before submitting? Is there a policy about unit testing? What is the policy on submiting changes into the -current tree for alpha and beta testing by the masses? Peace, ejc Disclaimer: I do understand what current is, I have rtfm. Just looking for constructive development ideas.