On 13/05/2015 13:39, Claude Frantz wrote:
Hi Claude,
> On 05/12/2015 02:00 PM, richard stanley wrote:
>
> Hi Richard,
>
>> it's in version 1.6.1 not 1.5 or 1.6.0
> Please explain me the relationship between these version numbers and the
> release numbers used by svn. David White has used r5353 and he mentioned
> version 1.6.1. I have used the later svn release 5355 but I'm still at
> version 1.6.0. Why ?
Subversion change set numbers (normally shows as rNNNN) are not release
numbers, they are a unique number that increments by one every time a
new change set is committed to the Subversion repository.
Different threads of development and release are kept on different
branches of the repository. For example the main development line for
WSJT-X lives in the ^/branches/wsjtx branch. The branch that is going
through a release cycle, i.e. preparing documentation, fixing any
outstanding serious issues etc. is the v1.5 branch and that lives in
^/branches/wsjtx-1.5. Joe is working on new features in a separate
branch so as to limit the disruption of the development branch. His
feature branch lives at ^/branches/wsjtx_exp. You can choose to check
out and build any of these branches, you will get a different result
depending on the branch you choose. A quick summary of the current branches:
^/branches/wsjtx-1.4 - the v1.4 release branch, a full GA release was
published from that at v1.4.0,
^/branches/wsjtx-1.5 - this is the proposed v1.5 release which as so
far had v1.5.0-rc1 published as a beta,
^/branches/wsjtx - this is the development line and will at
some point become the root of the v1.6 branch,
the development line
has the initial implementation of the VHF & up modes,
^/branches/wsjtx_exp - this is a feature branch and Joe K1JT is
integrating WSPR into it,
this will be merged
back into the development branch when it is stable,
probably after the
v1.6 branch is made but this isn't decided yet.
Subversion changeset numbers are not helpful in identifying branches
although they can be used to mark out progress in any particular branch
since they always increase with time of commit.
Hope this helps.
>
> Best 88 de Claude
73
Bill
G4WJS.
>> -----Original Message-----
>> From: Claude Frantz
>> Sent: Tuesday, May 12, 2015 12:08 PM
>> To: WSJT software development
>> Subject: Re: [wsjt-devel] WSPR mode in WSJT-X 1.6.1-devel
>>
>> On 05/12/2015 12:45 PM, David White wrote:
>>
>>> I used WSPR mode the past two nights with WSJT-X 1.6.1 r5353 and r5357.
>>> WSPR worked well in both receive and transmit, and I had no issues.
>> Here, svn is saying to be at revision 5355, but I cannot find a wspr
>> mode. What is or can be wrong ?
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
