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

Re: Win7 with 1.6.x (was: 1.7.0)

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Sun, 14 Feb 2010 21:57:40 +0000

On 14 February 2010 18:47, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> Hi,
>
> In the thread with subject "1.7.0", there wasn't really a consensus.
> Well, nobody objected to a release with new features, but there was
> quite a controversy about what version number to use for this. None of
> the suggestions really got a consensus.

But I think we were getting towards one.

> So I think the only way to solve this problem is to merge the changes we
> did to make TSVN work better on Win7 back to the 1.6.x branch and have
> it released there.

Not the only way, but it is certainly a way forward. How big a change
is the Win7 compat change?

> Since the Win7 changes are really the only changes that are important
> (users can live quite well without the other new features, even though
> they're great), we can keep the current version numbering scheme and
> avoid any confusion a new scheme might cause.

I think there is still a case for changing our numbering to split away
from SVN releases, and given a little more time I think we could find
a format that pleases (most) people. But there is no urgency for it to
happen now.

> So I'll start merging the important Win7 changes to the 1.6.x branch soon.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2447573
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-02-14 22:57:45 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.