[chirp_users] General: Updating CHIRP
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
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
On Wed, 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
There is a battery of tests done on each build before it is released. So technically each daily build released is the latest stable build.
If CHIRP is working well for you, you do not need to upgrade.
My rule of thumb for when to upgrade is... 1 when a bug that affects you has been fixed 2 when a feature that you want has been added 3 when you get a new radio
I subscribed to the developer mailing list and whenever there is a new build, I get an email sent to me letting me know of the new build and what the changes are (new radio support, bug fixes, added features, etc).
Jim KC9HI
I stand enlightened. Thanks! And, yes, the rev. I have runs like a deer in hunting season.
73 de KC3DOO Rick
My rule of thumb for when to upgrade is... 1 when a bug that affects you has been fixed 2 when a feature that you want has been added 3 when you get a new radio
Yep, this is a good checklist. I would add:
4. When you are bored
Otherwise, the above list stands :)
I subscribed to the developer mailing list and whenever there is a new build, I get an email sent to me letting me know of the new build and what the changes are (new radio support, bug fixes, added features, etc).
Just to be clear, the users list (this list) is the one that gets the build reports, with a changelog of what changed (and only what changed) in it. Users should generally not subscribe to the developer's list unless they like reading code :)
--Dan
Just to be clear, the users list (this list) is the one that gets the build reports, with a changelog of what changed (and only what changed) in it. Users should generally not subscribe to the developer's list unless they like reading code :)
My bad. Thanks for the clarification.
Jim
participants (4)
-
Bill Bartilson -
Dan Smith -
Jim Unroe -
Richard B. Emerson