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

RE: Automate the version number

From: Jon Daley <jon_at_limedaley.com>
Date: 2007-05-11 14:47:27 CEST

On Fri, 11 May 2007, Lübbe Onken wrote:
>>>> You also have to ensure that every client has the client side hook
>>>> installed.
>>> Correct, that will kill this feature for me, since the ones
>>> I care about the most are the clueless folks, not the developers.
>>
>> The client side hooks are only required if your build process is not
>> able to call SubWCRev.
>>
>> I am a little confused about your process now. Why are the clueless
>> folks using a subversion client anyway? Aren't they downloading from
>> your distribution rather than directly from the SVN repo?
>
> I'm slowly getting that impression too. You're on dangerous ground if you
> allow customers to run software directly off your repository.

         I missed the previous reply to this thread. Yes, some people just
grab the zipped release, and our build script replaces the version number
appropriately for those releases. But, we have some people that aren't
developers that have access to svn, and so simply run svn checkout and
svn update, and don't have any idea what it is doing. It is easier for
them to keep up to date with our latest stuff, without having to
redownload new packages all the time. FTP servers on the cheapo web
hosting places don't seem to work all that well, and so people are
constantly having trouble FTPing files to their host, and using subversion
gets around that problem. We make incremental patches from the prior
minor release to the next, and we have nightly builds, but having
incremental patches on a finer grained scale than the minor releases would
be pretty hard to manage. We also use sourceforge for our download
center, and it isn't the quickest interface in the world to upload to, so
I want to minimize developer time uploading files to sourceforge.

         As for it being "dangerous" to allow people read-only access to
the repository, I don't follow that logic. There is certainly more risk
if someone happens to update while the branch is undergoing more work.
The branches are generally pretty stable, and the trunk is pretty
unstable, until it gets close to a release, and people generally have a
decent idea how stable a particular branch or trunk is. We also encourage
people using subversion to be on the dev mailing list, so then they see
all commits, and the other developer comments on those commits.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri May 11 14:59:13 2007

This is an archived mail posted to the TortoiseSVN Users mailing list.