request a new release

[chenrui333]

it has been almost two years, and good to have a new release to include the recent changes. Thanks! (0.4.2 failed to build against rust 1.78.0)

[knedl1k]

up

[chenrui333]

cc @roderickvd

[roderickvd]

To cut a release I want to make sure that it’s running well and can get follow up support when issues come in. We owe that to our users who probably run this on thousands of devices.

I don’t use Spotify or even have an account on it anymore. So what we need are active contributors and maintainers.

I’m leaving on holidays without access to my development chain. If you guys can let me know who’ll be here to support a release when I cut one, it can be as soon as in three weeks.

[kingosticks]

Out of interest, what are you people requesting here? Small fixes i.e. v0.4.3 (would have to find what could be easily backported from dev, might not be much). Or a major release from the dev branch with the breaking api changes and major differences that come with it?

[kingosticks]

(because one requires minimal support, the other requires loads)

[chenrui333]

I would say both, but we can start the former and then move to the latter (maybe some beta releases before the actual major release as well.) generally, the more releases, so that the more people can test and give feedback.

[roderickvd]

I'd be up for a release after #1309. My point about depending on you guys remains.