Hi all,
We need to make a policy decision about how we store the source files
for our User Guides.
For WSJT-X the sources are currently found in these SourceForge directories:
.../branches/doc/wsjtx/source
.../branches/doc/wsjtx/images
This system has worked well in most ways, but does not readily
accommodate the fact that we currently have three active versions of WSJT-X:
WSJT-X v1.4.0 - about to be cleared for general availability
WSJT-X v1.5.0 - standard development branch; beta release soon
WSJT-X v1.6.0 - leading edge branch for incorporating the
VHF/UHF/Microwave/EME modes supported in WSJT
When we start to write new User Guide sections for v1.5 or v1.6, I guess
we'll need a new branch (or branches?) to accommodate them. Should we
make a v1.4.0 tag of the doc branch as it stands now, and call that the
"final" v1.4 manual? (Or should it be a branch, rather than a tag, so
as to make more obvious the possibility that further
additions/corrections might be made?)
The current .../doc/... branches (the ones listed above) would then
become the place for v1.5 additions and updates to the manuals. We'll
need to use distinguishable, version-specific file names in the URLs
used for their online access.
Does this make sense? Other suggestions?
-- Joe, K1JT
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
