Hi!
On the download page https://chirpmyradio.com/projects/chirp/wiki/Download it says, "Any time we make a change to CHIRP, a build is created for it the next day". There were three commits https://github.com/kk7ds/chirp/commits/master/ on March 29th but the latest build is from March 28th.
Is there a problem with the build system, or does the build not happen after each change?
Thanks! -Chris
On the download page it says, "Any time we make a change to CHIRP, a build is created for it the next day". There were three commits on March 29th but the latest build is from March 28th.
Is there a problem with the build system, or does the build not happen after each change?
This used to be the plan when we had less activity (and really comes from when I was processing patches on the ML). Often some of those would queue up, I'd apply them, and then there'd be a build the next day because even though there was some activity over the course of some time, me applying them was "the change". But, it's nicer to be able to merge PRs sooner (for the author) so I've started merging them to master and then periodically pushing that to the build-queue branch, which is what the build system looks for. I've been shooting for doing that Thursday nights, for a build on Friday, which has been pretty regular lately, although if there's a critical fix I'll push whenever.
So the statement isn't wrong, if you interpret "change to CHIRP" to be "change in the build-queue branch". But maybe I should tweak it to be a little less explicit.
--Dan
Thanks for the clarification. I think updating the download page to indicate that builds normally happen weekly would help...at least it would help me. :)
Thanks for all you do! -Chris
On Tue, Apr 1, 2025 at 8:08 AM Dan Smith via Developers < developers@lists.chirpmyradio.com> wrote:
On the download page it says, "Any time we make a change to CHIRP, a
build is created for it the next day". There were three commits on March 29th but the latest build is from March 28th.
Is there a problem with the build system, or does the build not happen
after each change?
This used to be the plan when we had less activity (and really comes from when I was processing patches on the ML). Often some of those would queue up, I'd apply them, and then there'd be a build the next day because even though there was some activity over the course of some time, me applying them was "the change". But, it's nicer to be able to merge PRs sooner (for the author) so I've started merging them to master and then periodically pushing that to the build-queue branch, which is what the build system looks for. I've been shooting for doing that Thursday nights, for a build on Friday, which has been pretty regular lately, although if there's a critical fix I'll push whenever.
So the statement isn't wrong, if you interpret "change to CHIRP" to be "change in the build-queue branch". But maybe I should tweak it to be a little less explicit.
--Dan _______________________________________________ Developers mailing list -- developers@lists.chirpmyradio.com To unsubscribe send an email to developers-leave@lists.chirpmyradio.com
participants (2)
-
Chris Mildebrandt -
Dan Smith