New release?

[mynona]

The last release was in June. There were a lot of commits meanwhile. When can we expect a new release?

[RBEmerson970]

Being blunt, one of this projects biggest shortcomings is version control. Given the volume of activity here, the version numbers should have changed more than once since June. That hasn't happened,

At this point, the [purported] V0.2.4 I currently use under Docker is almost certainly not the same as the [purported] V0.2.4 you're currently using. This comment excepted, I've given up on hoping some sense of order and version control will be applied to this project.

[remsky]

Definitely fair. Aiming to sort through what's needed and clean up the versions shortly.

Communication has been a little spotty on development, but have made a channel here to coordinate feedback

https://discord.gg/KGSQe8CUb

[RBEmerson970]

Please, please, PLEASE! For the love of all that's holy, get the version number right, and make it a visible part of the product!

And that means 0.2.4 is so over and done, and 0.3.0 is... done, too. Please pull the proverbial finger out, and use this newest update to get version numbers back under control!

Honestly, it is so hard to do that?

[remsky]

Hey @RBEmerson970, productive feedback is welcome, but this sure ain't it. This also isn't a product. It's a development project driven entirely by voluntary work from community members, including myself. I hope you'll keep future comments productive and with that in mind.

On the recent release: there's obviously been a divergence between master and release branches, etc, as you mentioned above. To start consolidating, fix up the GitHub build actions to make the naming more transparent, and avoid disrupting contribution histories too much, the current state was snapshotted to the -master suffixed images before further changes were made.

[RBEmerson970]

I stand by my now deleted message. Why use V0.2.4, which has been present for months, for a significant change in the product, project, whatever name applies (that's minor semantics)? Since V0.3.0 was present in VERSION in the past, that should ruled out, too. Again, is it so hard to implement at least nominal version identification?

…

On Sat, Dec 13, 2025 at 7:06 PM remsky ***@***.***> wrote: Hey @RBEmerson970 <https://github.com/RBEmerson970>, productive feedback is welcome, but this sure ain't it. This also isn't a product. It's a development project driven entirely by voluntary work from community members, including myself. I hope you'll keep future comments productive and with that in mind. On the recent release: there's obviously been a divergence between master and release branches, etc, as you mentioned above. To start consolidating, fix up the GitHub build actions to make the naming more transparent, and avoid disrupting contribution histories too much, the current state was snapshotted to the -master suffixed images before further changes were made. — Reply to this email directly, view it on GitHub <#418 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFI36ZDMIJOXGICSN5QKLGT4BSSYJAVCNFSM6AAAAACMLL2XP2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRUHA4TSNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[RBEmerson970]

Under Win 11, Docker 4.54.0, whatever was in master at 1900 EST 13 Dec 25 built and runs without a problem.

Previously reported FastKoko problems with file names, and inability to play back correctly past about 10:00 remain (comments will be added to existing threads).

The audio seems qualitatively slightly choppy compared a build from 15 Oct 25 (VERSION contains 0.2.4), but that's a purely subjective opinion.