Hi all,
We seem to be converging on a release procedure something like the
following:
1. Minor bug fixes and tweaks to the packaging scripts are OK, but from
today no new program features will be added to WSJT-X before we freeze
code for the candidate release of v1.4.
2. G4WJS may make a few more tweaks to the hamlib library. (Important
question for Bill: How will the state of that library be effectively
frozen into the tagged candidate release?)
3. By 00:00 UTC Sept 26, one week from today, we'll agree on the SVN
revision number of our mainline development branch,
".../branches/wsjtx", that will be tagged for the candidate release.
We'll call the tag something like ".../tags/wsjtx-1.4.0-rc1". Code in
this tag is frozen forever.
4. Code in the new tag will be checked out, compiled, and packaged on
each platform for which we'll provide a binary installation package. It
will also be made into a compressed source tarfile.
5. The tagged source code will be SVN-copied into a new branch,
something like ".../branches/wsjtx-1.4". Subsequent bug fixes to v1.4
will be made there, and (if applicable) merged into the main development
branch ".../branches/wsjtx".
6. On Oct 1 I will post the new source-code tarfile at SourceForge and
links to the binary packages (or instructions for obtaining and
installing them) on the WSJT Home Page.
7. The mainline development branch will be bumped to v1.5. Subsequent
development (new program features, etc.) will take place there.
Note: All of the above refers to WSJT-X only; activity in other branches
of our repository may continue normally.
Does this sound right? Have I got something wrong, or left out anything
important?
-- Joe, K1JT
------------------------------------------------------------------------------
Slashdot TV. Video for Nerds. Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
