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

Re: Use "1.7.7" for next release

From: Mark Phippard <markphip_at_gmail.com>
Date: Sat, 14 Apr 2012 18:04:01 -0400

On Sat, Apr 14, 2012 at 5:52 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 14.04.2012 23:46, Greg Stein wrote:
>
>>  > So I'll keep the first three version numbers the same in the future
>> for interim releases (in case I have to create one).
>>  > But I guess if you want to improve the current situation, there's not
>> much I can do.
>>  >
>>
>> Hyrum is suggesting we release 1.7.5, and you release 1.7.6.1. Then we
>> release 1.7.6, and tsvn goes to 1.7.6.2. Then we both bump to 1.7.7.
>
>
> Ok, but the TSVN version will have to be named 1.7.6-2, not 1.7.6.2 because
> the fourth number is the build revision. It's important that the fourth
> number keeps increasing with every version, otherwise the msi won't install
> correctly (we actually swap the third and fourth number for the msi because
> of that, otherwise nightly builds wouldn't install properly).

FWIW, I would say just do whatever you want. People will figure it
out. I do not see that this is a problem. Your downloads and about
dialog are very clear about the Subversion version.

With Subclipse we use odd/even version numbering so our current
version is 1.8.7. We have never tried to align with the Subversion
release number. That would be pointless as it would imply we can only
do releases when there are Subversion releases.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on 2012-04-15 00:04:33 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.