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

Re: 1.7.0

From: Daniel Atallah <daniel.atallah_at_gmail.com>
Date: Sat, 13 Feb 2010 12:54:29 -0500

On Sat, Feb 13, 2010 at 10:30, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> * we never ever stated that the TSVN version number is in any way linked
> to the svn library. It just happened to coincide, but that was just for
> convenience. And whenever svn 'skipped' a few micro versions (e.g.,
> 1.6.7 and 1.6.8 of the svn lib were never released), the version numbers
> didn't match anymore. Just look at the current official release: TSVN
> 1.6.7, linked to svn 1.6.9.

What I believe contributes to the confusion that people have is that
TSVN has historically bumped the minor version with the release of the
corresponding SVN minor release, and as far as I know, even most (of
course, not all) micro numbers have coincided.
So, while no attempt to keep SVN and TSVN version numbers synchronized
may have been made, the fact that they are so similar means that
someone who doesn't follow TSVN development closely will make the
(probably not unreasonable) assumption that there is a correlation.

> * the TSVN installer filename has *both* version numbers in it. The svn
> version it is linked against is mentioned in the installer name.
> Something other projects don't do and forces users to look it up on the
> website/release notes. With TSVN that's much easier.

This is certainly a good thing and I hope it continues.

> * That leaves two options to name the new version: 1.7.0 or 2.0.0. I'd
> like to go with 1.7.0 because we're still using the same svn lib. A
> major number change IMHO requires a lot more changes.
> * another advantage to have a new major/minor version number is that we
> get rid of the sync with the svn version number for good. I never was
> quite happy with that anyway, since it blocked us from having our own
> release timeframe.

The problem with using something like "1.7.0" is that people will
continue to have the same confusion as they do now because the numbers
are similarly structured and therefore seemingly connected.
In a few months when SVN 1.7.0 comes out, there are sure to be people
who will naively match the version numbers thinking that they are
related.

My suggestion (FWIW) is to use this opportunity to go for something
completely different and eliminate the potential for confusion.
"2.0" is a step in this direction, but when (if?) SVN 2.0.0 ever comes
out will once again be confusing.

-D

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2447315

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-02-13 18:54:35 CET

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.