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

Re: [TSVN] Re: Re: Re: Re: Nightly build readme.txt

From: SteveKing <stefankueng_at_gmail.com>
Date: 2004-10-25 10:34:25 CEST

On Mon, 25 Oct 2004 08:49:54 +0100, Simon Large <slarge@blazepoint.co.uk> wrote:

> Checking dll versions is not good! That's why we have an installer to do
> it for us ;-) I think this could lead to more email from confused users.
> Now they avoid a reboot, but will it work?

What I meant was: _you_ should check that if the last nightly build
was installed correctly. Not that every user would have to do that.

> I have only installed one nightly with the new scheme, and I did not get
> a new entry, but maybe I would if installed several?

We remove the previous version automatically when we install TSVN. So
that's why you don't get multiple entries.

> Suggestion, slightly less horrible this time:
> Always keep the same product ID to avoid multiple records in Add/Remove.
> Combine parts of the version number by using a x100 on one part.
> becomes
> 1.203.1858
> It is reasonably obvious what this is supposed to represent. It will
> only fail if there are > 99 bug fix releases (3rd digit) between feature
> releases (2nd digit), and the version number always increments.

I think we're getting way to far with this. Remember we're talking
about the nightly builds here, not the official releases. I think
people using the nightly builds are skilled enough to determine if the
installation went well or if they need to
uninstall/(reboot)/install/reboot to make it work.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Oct 25 15:49:47 2004

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

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