[chirp_users] What's next for CHIRP

bob burks
Sat Dec 31 17:48:33 PST 2022

Thank you for all the hard work you and other guys having the programming
intellect. Of which I have none. Taking two test during computer school
back in the 70's. Failed to grasp the computer programming skills. However
I was to be more technically incline to fix or repair any and all computer
Keep up the great work.
Bob KC4LB...

On Sat, Dec 31, 2022, 8:31 PM Dan Smith via chirp_users <
chirp_users at intrepid.danplanet.com> wrote:

> Hi all,
> I'd like to announce the availability of what I'm calling the "CHIRP-next"
> build for the new year. If you're not aware, some of the libraries that
> CHIRP depends on have been orphaned such that CHIRP was a bit stuck in time
> for many years. Overcoming this obstacle required a lot of changes to
> CHIRP's core, drivers, and the GUI has had to be completely rewritten as a
> result. This has been a ton of work, and we still have a lot left to do.
> However, it's time to rope you, the users and power users, into the
> effort. Several of us have tested hundreds of radios over the last few
> months getting ready for this, but we need your help to flesh things out.
> Over 90% of the radios that get used most often with CHIRP have been
> tested, but there are still plenty left that need to be confirmed (or
> fixed). Similarly, the GUI has been tested fairly well amongst the
> developers at this point, but there are surely still plenty of bugs to find
> and fix.
> Ultimately, this new build will become what is today the "daily" builds,
> and the current version of chirp will be renamed "legacy". As of now, all
> new development is being done on the "next" builds and only critical bug
> fixes will be considered for legacy. If CHIRP-next works for you and your
> radios, we want you running it as soon as possible.
> I've put together a page that describes in more detail why we're having to
> do this, how you can help, and what to look for and report:
> https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuild
> Also, here's a page that describes some of the changes you can expect in
> the new version:
> https://chirp.danplanet.com/projects/chirp/wiki/ChirpNextBuildChanges
> While we're not doing this specifically to add features, the "opportunity"
> to redesign some things has allowed us to add some improvements. Further,
> being on newer dependent libraries has allowed us to add some features we
> never had before.
> If you're on MacOS or Linux, you will almost certainly want to be running
> the new build immediately. It uses modern dependencies and also behaves
> much more like a native application on all platforms.
> We really need your help testing and vetting this new version, so if you
> feel comfortable, please consider giving it a try and letting us know what
> you run into. I'm getting the word out here to the users groups a little
> early, before we start offering it on the download page specifically. Feel
> free to forward this to your own groups, facebook pages, etc to get more
> visibility than just the users here.
> You can find the CHIRP-next builds here:
> https://trac.chirp.danplanet.com/download?stream=next
> As always, you'll want to stay up-to-date with these, as things have been
> moving fast!
> --Dan
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Bob at kc4lb1 at gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com
> To report this email as off-topic, please email
> chirp_users-owner at intrepid.danplanet.com
> Searchable archive:
> https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20221231/1d4ad914/attachment.html 

More information about the chirp_users mailing list