From: Jean-Michel POURE <jm@poure.com>
Reply-To: jm@poure.com
To: Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter_e@gmx.net>,
	Andrew Dunstan <andrew@dunslane.net>
Subject: Re: Build farm
Date: Mon, 24 Nov 2003 10:14:48 +0100
User-Agent: KMail/1.5.4
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
References: <Pine.LNX.4.44.0311191912530.21224-100000@peter.localdomain>
	<23062.1069440468@sss.pgh.pa.us>
In-Reply-To: <23062.1069440468@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200311241014.48813.jm@poure.com>

Le Vendredi 21 Novembre 2003 19:47, Tom Lane a =C3=A9crit :
> I think the main value of a build farm is that we'd get nearly immediate
> feedback about the majority of simple porting problems. =C2=A0Your previo=
us
> arguments that it wouldn't smoke everything out are certainly valid ---
> but we wouldn't abandon the regression tests just because they don't
> find everything. =C2=A0Immediate feedback is good because a patch can be
> fixed while it's still fresh in the author's mind.

Dear friends,

We have a small build farm for pgAdmin covering Win32, FreeBSD and most GNU/
Linux systems. See http://www.pgadmin.org/pgadmin3/download.php#snapshots

The advantage are immediate feedback and correction of problems. Also, in a=
=20
release cycle, developers and translators are quite motivated to see their=
=20
work published fast.=20

Of course, it is always hard to "mesure" the real impact of a build farm. M=
y=20
opinion it that it is quite positive, as it helps tighten the links between=
=20
people, which is free software is mostly about.

Cheers,
Jean-Michel Pour=C3=A9