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

Re: Announcing MaxSVN

From: Ivan Zhakov <ivan_at_visualsvn.com>
Date: Thu, 24 Sep 2015 12:29:39 +0300

On 24 September 2015 at 00:38, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Evgeny Kotkov wrote on Wed, Sep 23, 2015 at 21:12:19 +0300:
>> Stefan Hett <luke1410_at_gmx.de> writes:

[..]

>> So, why not have a scheme that uses tag names when you build from a tag,
>> branch names when you build from a branch, and trunk when you build from trunk?
>> You could split the builds in two separate groups when presenting to the user,
>> say, like this:
>>
>> MaxSVN 1.9.0-1
>> MaxSVN 1.8.14-1
>> MaxSVN 1.7.22-1
>> MaxSVN 1.7.21-1
>>
>> MaxSVN trunk-dev-r1704854
>> MaxSVN 1.9.x-dev-r1701565
>> MaxSVN 1.8.x-dev-r1701493
>> MaxSVN 1.7.x-dev-r1700845
>>
>
> I think it's useful to have the "latest released SVN_VER_PATCH" value in
> version number for easier reference. ("Is 1.7.x-dev-r1700845 before or
> after 1.7.22?") So perhaps:
>
> tag build: 1.8.14_0
> branch snapshot: 1.8.x-dev-14-r1701565 (where '14' is the latest released value of SVN_VER_PATCH)
>
> And in either case, optionally a build number at the end, if Stefan
> decides to include that.
>
Looks like acceptable solution for me.

-- 
Ivan Zhakov
Received on 2015-09-24 11:30:12 CEST

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