Hi Joe & All, we currently have the v1.5 branch of WSJT-X awaiting some documentation updates before making a new release candidate, although unrelated it would be nice to get that moving as well. The v1.5 branch has a few bug fixes since the RC1 release which need to be published. I would also like to move to generating the user guide as part of the WSJT-X build in the v1.5 branch as this addresses issues with the documentation being in line with the application, this will become very relevant as much needs to be done to the user guide with all the new capabilities. On this last point, there has not been much feedback on the trial implementation in the development branch so I think it is down to you Joe as to whether we go ahead with a combined user guide build.
Joe, are you proposing that the JT4 and other VHF and up features are released along with the WSPR features? I am a little uncomfortable with that as it is a lot of new content for one release and I suspect that both the JT4 tranche of work and the WSPR tranche both will have some destabilizing effect, do we want to move to supporting both in one release or would a phased release be easier to deal with? Having said that, I think the WSPR user base will be the larger one so a release adding just JT4 & VHF features may not get much traction. What is clear to me is that these new changes will bring two distinct new communities to WSJT-X, the WSPR beacon users and the VHF & up EME users. We must be careful not to underestimate the number of yet to be discovered issues that these users will uncover right through from fundamental defects to nuances that might deter them from upgrading from their current applications. 73 Bill G4WJS. On 22/05/2015 17:45, Joe Taylor wrote: > Hi all, > > I believe WSJT-X v1.6.1 now works well in all of its supported modes: > JT9, JT65(A-C), JT4(A-G), and WSPR-2. Surely there is more work to be > done: to name just a few items on my To Do list, WSPR-15 should be > implemented, message averaging should be added to JT65, and a higher > accuracy EME Doppler calculation should replace the present one, which > may have errors as large as 20 Hz at 10 GHz. Probably also some cleanup > and/or refactoring of source code, some "beauty-treatments" on the GUI > here and there, etc. > > I think these things can reasonably be done in our normal development > branch, so I'd like to suggest it's time to merge my "features branch", > aka .../branches/wsjtx_exp, aka v1.6.1, back into the main development > branch, .../branches/wsjtx. > > Is everyone OK with this plan? Among other advantages, it will mean > that our current SVN branches .../wsjt_exp, .../wspr, and .../wsprx will > become inactive. This will result in a considerable simplification in > the way we manage our source code and will minimize the required number > of cross-branch merges. > > -- Joe, K1JT ------------------------------------------------------------------------------ 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
