On Wed, Apr 22, 2009 at 11:40:42AM +0200, Bert Huijben wrote:
> I completely automated a Subversion build including downloading / checking
> out, compiling and in some places patching dependencies for the SharpSvn
> build in a fraction of that time. (All publicly available in
> http://sharpsvn.open.collab.net/svn/sharpsvn/trunk/imports, username guest,
> no password).
>
> Cleaning it up to be more generally usable (and moving it into the
> Subversion project) would be a nice task though.
+1 for moving this into our tree.
And having the same thing for other platforms.
I have a Makefile for BSD make that does the same thing.
I could try to polish that to provide general *BSD builds.
We need daily builds of trunk for our users to test.
I posted a patch to users@ yesterday, and asked for testing.
The response was: Can someone please compile this for me?
This is inhibiting progress. If we had an automated nightly build
for a couple of platforms the result of which are used by the buildbots
and end up somewhere on FTP, I could have just thrown this patch into
the nightly build. The patch would have been tested by now (at least
by the bots), and it would save a lot of people a lot of time and
hassle.
Insisting that source code is the only result of our work to the point
of making it hard for our users to test changes we make is not healthy.
Stefan
Received on 2009-04-22 13:35:44 CEST