Releases/Tags #8

caenguidanos commented 2026年04月18日 17:02:50 +02:00

Hi, why are not releases or tags to point to?

Hi, why are not releases or tags to point to?

BillyDM commented 2026年04月19日 03:17:00 +02:00

NIH-plug is still experimental software that is maintained with a "best effort" approach. There's no official version yet.

For now you can just depend on a specific commit hash like this:

nih_plug = { git = "https://codeberg.org/BillyDM/nih-plug.git", rev = "d9377be3b6" }

NIH-plug is still experimental software that is maintained with a "best effort" approach. There's no official version yet. For now you can just depend on a specific commit hash like this: ```toml nih_plug = { git = "https://codeberg.org/BillyDM/nih-plug.git", rev = "d9377be3b6" } ```

caenguidanos commented 2026年04月19日 10:49:06 +02:00

I understand, but what is happening in the audio field is an anomaly within the Rust ecosystem. For example, if there is not yet a Release 1.0.0 version — which is the strategy other projects follow, though not the only one — a note can be added to the documentation header stating that it is still in beta and under development.

This can have several positive effects: people will use this project more, and it will gain more visibility and more contributors. It also helps with versioning: what version of CLAP and VST3 does each version support? Where is that documented? Or has a specific version of CLAP/VST3 been set as the target to reach Release 1.0.0?

I believe there is an enormous effort behind this library (and others in the audio space, such as clack) and that great work has been done — but it is practically invisible.

Here is a project that uses the Release 1.0.0 strategy: https://github.com/timescale/pg_textsearch.

This project deserves to be on crates.io (and having it published there from the start also helps work out the distribution architecture from day one), and it deserves proper versioning.

Bests

I understand, but what is happening in the audio field is an anomaly within the Rust ecosystem. For example, if there is not yet a `Release 1.0.0` version — which is the strategy other projects follow, though not the only one — a note can be added to the documentation header stating that it is still in beta and under development. This can have several positive effects: people will use this project more, and it will gain more visibility and more contributors. It also helps with versioning: what version of CLAP and VST3 does each version support? Where is that documented? Or has a specific version of CLAP/VST3 been set as the target to reach `Release 1.0.0`? I believe there is an enormous effort behind this library (and others in the audio space, such as clack) and that great work has been done — but it is practically invisible. Here is a project that uses the `Release 1.0.0` strategy: https://github.com/timescale/pg_textsearch. This project deserves to be on crates.io (and having it published there from the start also helps work out the distribution architecture from day one), and it deserves proper versioning. Bests

caenguidanos commented 2026年04月19日 10:55:26 +02:00

About baseview: https://github.com/RustAudio/baseview/issues/227.

About `baseview`: https://github.com/RustAudio/baseview/issues/227.

BillyDM commented 2026年04月19日 18:11:01 +02:00

I understand the frustration, but the problem is baseview is kind of a buggy mess with fundamental architecture issues that no one has stepped up to maintain.

Right now baseview is more of a stop-gap until a better architected and better maintained plugin windowing library comes along, like Coupler: https://github.com/coupler-rs/coupler

Maybe the owner of baseview might consider just releasing a crates.io version anyway? It's their call though.

I understand the frustration, but the problem is baseview is kind of a buggy mess with fundamental architecture issues that no one has stepped up to maintain. Right now baseview is more of a stop-gap until a better architected and better maintained plugin windowing library comes along, like Coupler: https://github.com/coupler-rs/coupler Maybe the owner of baseview might consider just releasing a crates.io version anyway? It's their call though.

Sekwah commented 2026年05月22日 13:29:54 +02:00

Could consider organizing releases via tool like release-please or organize it with conventional commits just so its easier for people to know whats been added between versions or help align with checking out bugs on specific versions rather than commit hashes.

Shame that codeberg doesnt really have automated actions in the same way that are hosted to my knowledge because it could be handy to automate even if the versions were being like 0.1.5 prior to what would be considered a stable release.

Could consider organizing releases via tool like release-please or organize it with conventional commits just so its easier for people to know whats been added between versions or help align with checking out bugs on specific versions rather than commit hashes. Shame that codeberg doesnt really have automated actions in the same way that are hosted to my knowledge because it could be handy to automate even if the versions were being like 0.1.5 prior to what would be considered a stable release.

BillyDM commented 2026年05月30日 03:13:23 +02:00

Once #29 is finished, we will be able to publish all of nice-plug to crates.io! :)

Once #29 is finished, we will be able to publish all of nice-plug to crates.io! :)

BillyDM commented 2026年06月04日 21:25:41 +02:00

nice-plug has been published to crates.io!

nice-plug has been published to crates.io!