[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: 1.7 Release Plan

From: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Thu, 29 Jul 2010 18:40:41 +0100


> -----Original Message-----
> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
> Sent: Thursday, July 29, 2010 12:08 PM
> To: Hyrum K. Wright
> Cc: Talden; Subversion Development
> Subject: Re: 1.7 Release Plan
>
> On Thu, Jul 29, 2010 at 04:43, Hyrum K. Wright
> <hyrum_wright_at_mail.utexas.edu> wrote:
> > The project doesn't typically provide binaries, partly because there
> > are so many different combinations that it's hard to justify which
> > ones to build and which not too.
> >
> > However, providing binaries of these releases may be really useful,
> > especially for people in your position.  I *really* hope that our
> > volunteer packagers chose to build binaries of these interim releases
> > (with the appropriate warnings, of course).  It would also be nice if
> > third-parties (such as Tortoise) used these as part of their own beta
> > processes.
>
> TortoiseSVN already uses the svn trunk code (right now, about two
> weeks old) for its current nightly build releases. Of course, due to
> the wc format change, not many people are using it.
>
> Our build and upload script also provides builds of svn.exe,
> svnadmin.exe and svnserve.exe for people to use if they like:
> http://nightlybuilds.tortoisesvn.net/latest/

And may I say that Stefan's build scripts are "teh win". I had Tortoise downloaded and built, with all those dependencies in a matter of minutes. It was a thing of pure beauty.

FYI, he uses Nant, and if there was an case for an alternative build system, I can only suggest using Ant (which is mostly-but-not-quite related to Nant - see http://it.toolbox.com/blogs/paytonbyrd/ant-a-primer-for-nant-users-5772 for some conversion details).

Received on 2010-07-29 19:41:18 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.