Date: Thu, 23 Feb 95 11:00:20 MST From: terry@cs.weber.edu (Terry Lambert) To: phk@ref.tfs.com (Poul-Henning Kamp) Cc: jkh@freefall.cdrom.com, nate@trout.sri.mt.net, current@freefall.cdrom.com Subject: Re: TRUE and FALSE Message-ID: <9502231800.AA03444@cs.weber.edu> In-Reply-To: <199502230308.TAA07194@ref.tfs.com> from "Poul-Henning Kamp" at Feb 22, 95 07:08:48 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Get off of it. This always comes up, and all it does is ruffle > > > feathers. You don't have to be release engineer to understand some of > > > the issues required to do it. Heck, all of us do (our at least should > > > > Some of the issues, perhaps. Significant grasp of enough of them to > > argue this with me? No. Sorry, but no. You can change my mind by > > doing one thing and one thing ONLY, and that is to do a release or > > even a snapshot of your own and then come back to me with a > > description of what you did and how you did it. Otherwise I simply am > > I tend to agree here, and I belive Rod will agree. We have to cut the > effort to make a sterilized release from the present level to something > more managerable. Agreed! Anyone should be able to roll a release by typing "make release" somewhere! Not that everyone *should* be doing this, and not that this *should* be done without regression testing before plopping it into an FTP archive somewhere. The grunt work of the release has got to be the regression testing to make sure that what got rolled really installs somewhere. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9502231800.AA03444>