As I understand it, the code itself (written in python) is quite mature and stable.
The updates are centered around adding support for new radios and new radio variants, and also when bugs (usually related to the behavior of a specific radio or variant in the wild) are squashed.
So the best build is always the newest one available…
It worked out of the box for me the first time and I’ve never seen or experience a bug of any kind in my (very limited) use.
So unless you have a radio that is not supported, I don’t think you could fairly call yourself an alpha or beta tester.
My understanding is that the functionality of CHIRP meets or exceeds the functionality of paid software in most cases.
The fact that it’s working for what you (and I) need is a testament to that fact.
Does that answer your question? The short answer is that ALL releases are now production ready and stable, to the degree that you are asking the question.
-B
On Aug 10, 2016, at 9:21 PM, Richard B. Emerson pavilion@pinefields.com wrote:
How are non-alpha/beta updates handled? That is, given all the daily releases (i.e., alpha testing), is there ever a "looks pretty stable to me" release? What I've got now does what I need done (very well - good on ya!). OTOH, a new release might do something useful that I don't have in the release I use. But I prefer not to do alpha or beta testing if I can avoid it. So... how often does a stable release come out?
73 de KC3DOO Rick
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Bill Bartilson at bill@mandytech.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com