From owner-freebsd-hackers  Wed Oct 16 18:16:14 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA20549
          for hackers-outgoing; Wed, 16 Oct 1996 18:16:14 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA20543
          for <FreeBSD-hackers@FreeBSD.org>; Wed, 16 Oct 1996 18:16:11 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id SAA01238; Wed, 16 Oct 1996 18:16:07 -0700 (PDT)
To: Wilko Bulte <wilko@yedi.iaf.nl>
cc: FreeBSD-hackers@FreeBSD.org (FreeBSD hackers list)
Subject: Re: volunteering (was: putting 'whining' to work) 
In-reply-to: Your message of "Thu, 17 Oct 1996 00:10:26 BST."
             <199610162310.AAA02978@yedi.iaf.nl> 
Date: Wed, 16 Oct 1996 18:16:07 -0700
Message-ID: <1236.845514967@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> 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.

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.

					Jordan