On Fri, Dec 17, 2010 at 04:42:16PM -0500, r...@elilabs.com wrote: > Any idea why TSVN 1.6.12 Build 20536 2010/11/24 claims to be using SVN > 1.6.15 before it was released?
TortoiseSVN doesn't follow skips in version numbers that occasionally happen between Subversion releases. E.g. the entry for 1.6.14 in https://svn.apache.org/repos/asf/subversion/trunk/CHANGES reads as follows: Version 1.6.14 (Not released, see changes for 1.6.15.) This means Subversion 1.6.14 did not pass pre-release testing and wasn't made publicly available. Because TortoiseSVN releases don't use the same version numbers as the Subversion releases they're based on, TortoiseSVN users need to look at the "based on Subversion release X" number to find out which version of Subversion release they are using. (In case this relationship is unclear: TortoiseSVN, like virtually every other Subversion client out there, is a wrapper around the Subversion core libraries.) Even if TortoiseSVN did skip release numbers skipped by Subversion, release numbers could get out of sync if TortoiseSVN issued a release to fix a bug that's present in TortoiseSVN but not in Subversion. It's unlikely that we're ever going to see version numbers for both the Subversion core and TortoiseSVN increase in lock-step. Stefan