AW: Use "1.7.7" for next release
From: Markus Schaber <m.schaber_at_3s-software.com>
Date: Mon, 16 Apr 2012 08:02:26 +0000
Hi
Von: Daniel Shahaf [mailto:d.s_at_daniel.shahaf.name]
> > After sleeping on this, I'm also quite concerned about not
SharpSVN currently is on version 1.7004.2064, where the second number of the tuple is a combination of the second and third tuple of the upstream SVN number, and the third number is the sharpsvn revision / build number.
TortoiseSVN could maybe adopt a similar scheme. It can be adopted in the next build without decreasing any version number, and it also makes it obvious that an user with "SVN Version 1.7004.42" is not referring to plain svn, but some derivate.
Of course, this scheme will run into problems when SVN someday releases 1.7.1000, 1.65.535 or 1.66.0. :-)
Best regards
Markus Schaber
-- ___________________________ We software Automation. 3S-Smart Software Solutions GmbH Markus Schaber | Developer Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50 Email: m.schaber@3s-software.com | Web: http://www.3s-software.com CoDeSys internet forum: http://forum.3s-software.com Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915Received on 2012-04-16 10:03:07 CEST |
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.