<Ralph[m]>
new release ready and if they get no complaints for a few months they'd publish it as 1.0), so maybe i could do v0.3.0 now and have v1.0.0 early next year? or maybe i'm overthinking this and should just do v1.0 now and v2.0 when they do their releases? 🤔
<jannic[m]>
I wouldn't think too much about this decision. Do whatever you prefer personally. (Or ask people who actually use the crate and can tell if it feels mature enough for 1.0)
<jannic[m]>
Both 0.3->1.0 and 1.0->2.0 would be breaking changes, so it doesn't make any difference technically.
<jannic[m]>
If you want to avoid that breaking change, you could rename the features to `defmt03` and `rgb08`, and keep them indefinitely, and later add new features `defmt` and `rgb` for the 1.0 releases. Adding new features is not a breaking change, so could release 1.0 now, and the later release with the new features could be 1.1. But I guess now I'm overthinking this :-)
<jannic[m]>
* change, so you could release
<Ralph[m]>
i think for this crate using versioned features is an overkill. honestly, i don't even know who's using it (crates.io does show some downloads, so it's not completely unused 😅)
<Ralph[m]>
i guess i'll go for 1.0 now as the dependencies are optional and this way we have another 1.0 embedded crate 🙂