Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

Next preview release?

VA7LWE
VA7LWE Member
edited June 2020 in SmartSDR for Windows
Are we to expect a new preview release before V1, or is 0.13.10 the last stop before the destination?

Answers

  • Tim - W4TME
    Tim - W4TME Administrator, FlexRadio Employee admin
    edited March 2017
    Hopefully. SmartSDR v0.15.12 was released to alpha testing this evening.
  • KB5XE
    KB5XE Member
    edited September 2013
    Tim, what happened to v0.14.xx? Did I miss a beta version?
  • Tim - W4TME
    Tim - W4TME Administrator, FlexRadio Employee admin
    edited March 2017
    SmartSDR v0.14 did not pass quality testing therefore it was not released to the Preview group. http://community.flexradio.com/flexradio/topics/is_version_v0_14_3_coming_out_today
  • Ken - NM9P
    Ken - NM9P Member ✭✭✭
    edited June 2020
    It makes sense that if your internal testers found serious bugs, you don't need to send it out to the "preview release" bunch just so we can find the same bugs....(and cause you to spend extra time responding to US instead of fixing them). But I wouldn't mind playing with some of the new features even if there are bugs...UNLESS fixing some things broke some other things even worse.... (;o)
  • Nick
    Nick Member ✭✭
    edited July 2019
    I agree. If you go to some of the S/W development sites you see several versions available. There is usually the stable version, the last released version, and the latest builds (which are never stable). It would be interesting to see what you are working on next. The only problem is that without the source code we can't help get the bugs out!
  • Eric-KE5DTO
    Eric-KE5DTO Administrator, FlexRadio Employee admin
    edited February 2017
    Honestly, we have tried this strategy in the past. The issue is that we end up spending an inordinate amount of time supporting the unstable versions despite any warnings we put in the docs or the software itself. As a software developer, I'd love to get our code out there and tested by more people more quickly. But we can't do that at the risk of overwhelming our support organization. We're open to ideas of how to improve this, but simply putting warnings in the software and release notes has failed to tame the support burden of putting software with known issues into the field.
  • W4YXU
    W4YXU Member
    edited April 2016
    Perhaps the software could temporarily be like windows (heaven and other deities please forbid!) and call home while being installed. Then when someone enters a nastygram about the software and the version he last installed is pre Alpha level etc. a reply nastygram could be sent without human intervention!

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.