On 12/30/2014 5:32 PM, Dan Smith wrote:
That would technically be 0.5.0 based on our previous release criteria.
[...]
Yeah, how about we drop the "stable" releases entirely and start having people just download the latest *build*?
[...]
Thoughts?
I think that will probably work well. However: Given the nature of the problem with the Baofeng varients, as a precaution, I suggest pushing out the 0.5.0 release FIRST.
1. The new release will hopefully trigger anyone who is packaging CHIRP to wake up and notice the new major release, update their packages/distros.
2. The news of the new release will wind up notifying more people that the release process has changed, rather than waiting for them to poll the web site.
This will hopefully help stamp out many of problematic old versions.
My $.02, --Rob