Date: Thu, 17 Oct 1996 21:49:09 +0100 (MET) From: Wilko Bulte <wilko@yedi.iaf.nl> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: FreeBSD-hackers@FreeBSD.org Subject: Re: volunteering (was: putting 'whining' to work) Message-ID: <199610172049.VAA01397@yedi.iaf.nl> In-Reply-To: <1236.845514967@time.cdrom.com> from "Jordan K. Hubbard" at Oct 16, 96 06:16:07 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Jordan K. Hubbard wrote... > > So, lets assume I'd like to help in testing. What would be a > > workable way to contribute? Would I have to track -current? > > That would be the minimum requirement for at least *one* of your > machines, e.g. the release builder. > > What a lot of folks have been doing, and it makes a good sense, is > tracking the CVS repository and whenever I say that I'm making a > release, they make one too and test from that one. That saves them > from having to FTP my entire release across the pond, and they can > even make small test alterations to their local release build when > working collaboratively with me to solve a problem. OK. My assumption proved valid. > If you wanted to be truly labor-saving about it, I guess one person in > each network community could build the release and the others could > use the single central copy for testing. This would then be a sort of test-snaps ;-) And it would sure mean a lot of work for this test-manager. How big would such a test-snap be (in Mb) ? Assuming bin only, etc. Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda --------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610172049.VAA01397>