Next preview release?

  • 2
  • Question
  • Updated 6 years ago
  • Answered
Are we to expect a new preview release before V1, or is 0.13.10 the last stop before the destination?
Photo of VA7LWE


  • 34 Posts
  • 5 Reply Likes

Posted 6 years ago

  • 2
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9197 Posts
  • 3557 Reply Likes
Hopefully. SmartSDR v0.15.12 was released to alpha testing this evening.
Photo of KB5XE


  • 12 Posts
  • 0 Reply Likes
Tim, what happened to v0.14.xx? Did I miss a beta version?
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9197 Posts
  • 3557 Reply Likes
SmartSDR v0.14 did not pass quality testing therefore it was not released to the Preview group.
Photo of Ken - NM9P

Ken - NM9P

  • 4239 Posts
  • 1351 Reply Likes
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)
Photo of Nick


  • 48 Posts
  • 2 Reply Likes
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!
Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 912 Posts
  • 343 Reply Likes
Official Response
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.
Photo of W4YXU


  • 75 Posts
  • 6 Reply Likes
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!

This conversation is no longer open for comments or replies.