Hi,
Am 13.02.2010 14:05, schrieb Simon Large:
>
> There is certainly precedent for *not* staying in sync.
> 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
>
I'm not sure, if in those there is a dependency on WC version like for SVN.
I think user should not to have to read the release notes for
compatibility reason.
IIRC WC version changed more or less synchronized with the major/minor
version of SVN.
Please don't leave this good practice.
See Microsoft and Java: Inside same major version data sources, API and
features are compatible/unchanged.
What's the problem to have new features in a micro release as 1.6.10?
BTW:
At Sun, the GUI toolkit versions are synched to the command line
versions, e.g. NetBeans 6.x IDE is synchronized with JDK 6.x.
In my opinion this is good practice.
Another thought:
Why not start a new major numbering? Sticking on the same major version
for too long makes the major version number superfluous/ridiculous.
They have done it in Java, and Microsoft did similar.
E.g. Java 1.6 now is Java 6.0, MS Word jumped from 2.0 to 6.0 to
synchronize the versions in same Office package.
So go for 6.0, SVN should be convinced to to the same. I'm afraid, we
never will have version 2.x or more.
-Ulf
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2447320
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-02-13 19:19:12 CET