[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: version numbering

From: Lübbe Onken <luebbe.tortoisesvn_at_googlemail.com>
Date: Mon, 16 Apr 2012 09:52:01 +0200

Hi Folks,

I'd like to add my two cents as well. I have two suggestions:

A) Try to stay compatible with the SVN numbering scheme:
How many TortoiseSVN micro versions do we usually have per Subversion
release? Would it hurt us to use the svn release number as it is and just
become a sub-index in the third digit instead of adding a dash or a fourth
SVN 1.7.8 is released and every TSVN release based on SVN 1.7.8 has a
number of 1.7.8x, where x=[0..9] or 1.7.8xx xx=[00..99]
Since we are currently two micro versions ahead, we could go with
1.7.620, 1.7.630 until SVN catches up.
I don't like this very much, because it would sacrifice our own identity ;)

B) Give up compatibility and just give the users a hint against which SVN
release TSV is linked:
Use the first digit (major) of the numbering scheme for TortoiseSVN, and
only TortoiseSVN. Increment the third digit (micro number) for bugfix
releases. E.g. TSVN 2.x.0
Use the second digit (minor) for the SVN version without the dots. E.g. SVN
1.7.5 -> 175
So the next TortoiseSVN release linked against SVN 1.7.5 could be called
TSVN 2.175.0. We then have a lot of micro numbers for bugfix releases and
when svn moves to 1.8.0, we just start over with the micro numbers again,
e.g. TSVN 2.180.0.

- Lübbe

Please help me get more space on Dropbox :)
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net  PGP Key ID 0x23F511AB
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-04-16 09:52:06 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.