On Sun, Apr 15, 2012, at 11:28, Stefan KÃ¼ng wrote:
> On 15.04.2012 04:15, Daniel Shahaf wrote:
> > Konstantin Kolinko wrote on Sat, Apr 14, 2012 at 23:24:57 +0400:
> >> 2012/4/12 Daniel Shahaf<danielsh_at_apache.org>:
> >>> We released 1.6.18 today and 1.7.4 just over a month ago. There are
> >>> a few useful items merged already, and STATUS has a truckload of pending
> >>> changes.
> >>> Shall we roll 1.7.5 in two weeks from today? If we can clear STATUS and
> >>> roll next Thursday that's fine too, but I don't think we're in a hurry.
> >> Hi!
> >> I have a proposal:
> >> Skip several numbers and name the next release as "1.7.7".
> >> Justification: to align with TortoiseSVN, which is 1.7.6 now.
> > To summarize, the next release will be called 1.7.5 and Stefan KÃ¼ng will
> > change tsvn's versioning scheme to
> > "%d.%d.%d-%d" % (SVN_VER_MAJOR, SVN_VER_MINOR, SVN_VER_PATCH, tsvn_counter++).
> > Thanks for raising this (and thanks Stefan for the fix his end).
> Ahem: as I said I can not go back a version. I can't name the next TSVN
> release 1.7.5-2 since we're already have version 1.7.6 out.
I am not concerned about what how you call the tsvn releases that
correspond to svn 1.7.5 and 1.7.6, if the ambiguity problem is solved in 1.7.7+.
Apologies if I was putting words in your mouth, I was trying to
summarize my reading of the consensus elsethread.
> After sleeping on this, I'm also quite concerned about not incrementing
> the TSVN version since this would confuse our users a lot, not to
> mention the problems we would get on our mailing list.
> I'll start a discussion on the TSVN dev list about this first, before I
> can make a decision.
FWIW: I'd be happy with any scheme that doesn't confuse people between
TSVN's version number and SVN's version number. The specific numbering
scheme (1.7.7.x or 2.7.x or "1.7.x/1.7.y" or something else altogether)
is less important to me.
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net
Received on 2012-04-15 11:44:38 CEST