Re: 1.7.0

Hi,

On 13 February 2010 15:27, Ulf Zibis <Ulf.Zibis_at_gmx.de> wrote:
> +1
>
> May be call it 1.6.10.
> (Example: When Sun's Java SDK had a big enhancement, they jumped from
> 1.6u7 directly to 1.6u10)
>
> ... and later 1.6.18 when linked against SVN 1.6.8
> Or: 1.6.100 ... 1.6.108
>
>  > There is certainly precedent for *not* staying in sync.
> - "1000 flies won't be in error"  IOW: others should follow TSVN's good
> example
> - TSVN users are used to have the versions synched since long, so they
> probably would be more irritated and astonished than others.
>
>  > TortoiseHG 0.9.3 links against Mercurial 1.4.3
>  > TortoiseGit 1.3.x uses gitdll 1.6.x
>  > TortoiseCVS 1.10.x uses CVS 1.11.x
>
> This could express, that those T versions are in delay, offering ALL lib
> features in their GUI.
> ... but vice-versa doesn't make sense.
>

If you want to abandon the link between TSVN major and SVN major
version (so no more TSVN 1.n == SVN 1.n), then I would suggest to go
to TSVN 2.x and link to SVN 1.y. There should be no confusion then.

Having a TSVN 1.7.x that links to SVN 1.6.y, and after that TSVN 1.8.n
that will link to SVN 1.7.m will be confusing for an indefinite
period.

An alternative can be to temporarily lift the 'branch 1.x receives bug
fixes only' rule until SVN is ready to release new versions more
frequently again.

I would go for 2.0 and disconnect the TSVN versioning scheme from the
SVN releases.

-- 
Regards,
Jean-Marc
--
.       ___
.  @@  // \\      "De Chelonian Mobile"
. (_,\/ \_/ \     TortoiseSVN
.   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
.   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2447288
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].