Date: Wed, 28 Feb 1996 08:16:57 -0500 From: ejc@nasvr1.cb.att.com To: freebsd-current@freebsd.org Cc: dob@nasvr1.cb.att.com Subject: -current submitting policys Message-ID: <9602281316.AA14142@ginger.cb.att.com>
next in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9602281316.AA14142>