On 31/01/2014 20:50, Joe Taylor wrote:
Hi Joe,
John --
John Nelson wrote:
I have downloaded r3673 and it is running undertest - but I notice
you have made improvements regarding Type 1 and 2 messages and
genStdMsgs() - but this is r3677.
Do want these improvements to be excluded from the new release?
I agree it seems slightly awkward, but I decided this morning to
release the well-tested code (r3673) and then make the mods for
auto-generation of messages with complex callsigns. So yes, I'm
recommending that the released version be 3673.
It is best practice to tag milestones like releases in the repo. For
example the command (assuming you use ssh access to the repo):
svn copy -r 3673
svn+ssh://[email protected]/svnroot/repos/wsjt/branches/wsjtx
svn+ssh://[email protected]/svnroot/repos/wsjt/tags/wsjtx-1.3 -m
"Tagging WSJT-X release version"
will tag r3673 for ever more as the 1.3 release of WSJT-X.
That way there is no need to remember which revision represents a
milestone and later defect fix release branches can be created by
copying the tag back to 'branches'.
svn copy is cheap in that no actual files are copied on the server, only
changes to files use 'file space'.
More complex tags can be created if required, for example the discussion
on kvasd binaries is relevant in that the revisions of kvasd used for
the release could also be included in the tag by using the more
comprehensive "build a workspace from various revisions and tag the
workspace contents" version of svn copy. Having said that the
svn:externals property is a much better way of handling mapping of
external files from elsewhere in a repo to a tree in a repo and would
suit the kvasd situation where the binaries are used in multiple projects.
-- Joe
73
Bill
G4WJS.
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
