Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EF532118E9 for ; Mon, 7 Jul 2014 13:46:31 +0000 (UTC) Received: (qmail 3250 invoked by uid 500); 7 Jul 2014 13:46:31 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 3216 invoked by uid 500); 7 Jul 2014 13:46:31 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 3203 invoked by uid 99); 7 Jul 2014 13:46:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jul 2014 13:46:31 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of andy.levy@gmail.com designates 209.85.220.52 as permitted sender) Received: from [209.85.220.52] (HELO mail-pa0-f52.google.com) (209.85.220.52) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jul 2014 13:46:26 +0000 Received: by mail-pa0-f52.google.com with SMTP id eu11so5416955pac.25 for ; Mon, 07 Jul 2014 06:46:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ADGqYfHg+8VdO0i1Kl2HI2jmSe3iO+oF+hhLe23NU2c=; b=zBnBvEE8XGhgf15YJuSNIbBBCvI0FmpDyFSPpByvLDPtCT0QMyHRKpbbyYg3whbjBG jcE6Z29k/8bQ56IeoaPdxkjepiRdngK9BcKaNNqnyRD4nHeUmJZHxDksDQA377G+bT+C gU17qwEpz7ZbLq5Ko5Jz9U1LD0iX4lPiCZG9uYd8SBotFF+obPJspz2OamOM8KK85xsK qY7D91UBNicdCTpxmpc8mLpUoLnn5BlkQYGnqMyMMCmatpA4BhRPA7fg0zfvm+ebk8xt KtuyoMox8vb/9dctfFg56lL2OTA9awSIcL93b1q4r7ZV7LECZZs5ntZNFm7TVARFFder uBjA== X-Received: by 10.68.131.230 with SMTP id op6mr29257455pbb.55.1404740766248; Mon, 07 Jul 2014 06:46:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.85.40 with HTTP; Mon, 7 Jul 2014 06:45:26 -0700 (PDT) In-Reply-To: References: <043e01cf95e0$bd56f7c0$3804e740$@qqmail.nl> <53B525AD.903@wandisco.com> <20140703154731.GB2400@larry.stsp.name> <9775EDB6-9D6F-4510-8061-E5AE79612659@gmail.com> From: Andy Levy Date: Mon, 7 Jul 2014 09:45:26 -0400 Message-ID: Subject: Re: Extend E155021 message to include supported format version To: Notes Jonny Cc: Mark Phippard , =?UTF-8?Q?Branko_=C4=8Cibej?= , "users@subversion.apache.org" Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Jul 7, 2014 at 9:40 AM, Notes Jonny wrote: > On Fri, Jul 4, 2014 at 4:51 PM, Andy Levy wrote: >> On Fri, Jul 4, 2014 at 11:16 AM, Notes Jonny wrote: >>> Hi Mark >>> >>> You are right that I did have 1.8.x installed. Which I downgraded to >>> this version: >>> >>> TortoiseSVN 1.7.7, Build 22907 - 32 Bit , 2012/05/15 12:16:05 >>> Subversion 1.7.5, >>> apr 1.4.6 >>> apr-utils 1.3.12 >>> neon 0.29.6 >>> OpenSSL 1.0.1c 10 May 2012 >>> zlib 1.2.7 >>> >>> NB. I don't know why tortoise is called 1.7.7 and subversion uses >>> 1.7.5 - would be simpler if they matched. >> >> TortoiseSVN release 1.7.7 is built on Subversion version 1.7.5. >> Because there may be bugs in TSVN that aren't present in the >> Subversion libraries, there may be multiple TSVN releases for a given >> version of the Subversion libraries. >> >> For example, TSVN 1.7.2, 1.7.3 & 1.7.4 were all built on Subversion >> 1.7.2; TSVN 1.7.2 had some nasty bugs that needed to be resolved >> quickly (and 1.7.3 had one more). From the release announcement for >> 1.7.3[1]: >> >> Due to some nasty bugs in TortoiseSVN 1.7.2 which in some specific >> situations could make it crash, we're releasing this version out of sync >> with SVN releases. >> >> 1.7.4 had another bug that needed quick resolution[2]. >> >> The alternatives I can think of offhand are: >> >> 1) Only release TSVN in lock-step with Subversion releases, leaving >> TSVN bugs hanging in the wild unnecessarily long >> 2) Don't publish the library versions used in TSVN. This makes >> debugging & error reporting tougher >> 3) Don't bump the TSVN version number. This makes support tougher - >> are we using the first release of 1.7.5 or the second one? >> 4) Add yet another level to the version number scheme? 1.7.5.0, 1.7.5.1, etc.? >> >> The current scheme is fine IMHO. >> >> [1]: http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2894038 >> [2]: http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2908607 > > Hello > > Many thanks for the replies. > > It sounds like the TortoseSVN team want to keep things roughly "lock > step", I think better to be "completely lock step". > > I would go with: TortoiseSVN_1.7.5_Build001 > > Just increment the Build number when they make an updated delivery of > TortiseSVN that uses svn1.7.5 > > Its more confusing to use a similar but different numbering scheme > (1.7.7 and 1.7.5) in my view. I personally see nothing wrong or confusing about the system the TSVN folks have settled on. If anything, I think your suggestion would lead to more confusion, having to ask people *which* 1.7.5 they're using. What do you mean, 1.7.5 doesn't always mean the same thing? If you'd like to lobby for a change, you'll need to take it to the TSVN mailing list; how TortoiseSVN is managed seems to be quite off-topic on the SVN Users mailing list.