[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: Jean-Marc van Leerdam <j.m.van.leerdam_at_gmail.com>
Date: Sun, 15 Apr 2012 11:48:29 +0200


Op 15 apr. 2012 11:37 schreef "Stefan Küng" <tortoisesvn_at_gmail.com> het
> Hi,
> Currently, the TSVN version is 1.7.6 while svn is at 1.7.4. So we're two
> micro versions apart.
> This apparently causes some problems on the svn mailing lists.
> It was suggested that svn therefore would skip two micro versions for
> their next release to catch up with TSVN, but that suggestion was
> rejected. Instead TSVN should instead change its version numbering to
> avoid confusion.
> The discussion on the svn dev list is here:
> http://thread.gmane.org/gmane.comp.version-control.subversion.devel/135106
> So instead of our next release being 1.7.7, it would be 1.7.6-2 and when
> svn 1.7.7 gets out, we would be at 1.7.6-3,

1.7.7-1 would be better I think.

> and finally with svn 1.7.8
> we then would also be at 1.7.8.
> I'm not sure if this won't cause problems for us, since our users are
> used to only three digit numbers and might overlook the '-2' when
> reporting issues.
> So what do you think? Should we change our version numbering? Or just go
> on as we did before?

I agree with the new proposal, or you should completely severe the version
numbering. Maybe use the svn minor version as our major (TSVN 7.6.x linked
against SVN 1.7.6).
Once SVN reaches 2.0, jump to TSVN 20.0)

My 2ct.



To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-04-15 11:48:33 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.