Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

request a new release #1279

Open
chenrui333 opened this issue May 7, 2024 · 10 comments
Open

request a new release #1279

chenrui333 opened this issue May 7, 2024 · 10 comments

Comments

@chenrui333
Copy link

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
Copy link

knedl1k commented Jul 25, 2024

up

@chenrui333
Copy link
Author

cc @roderickvd

@roderickvd
Copy link
Member

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
Copy link
Contributor

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
Copy link
Contributor

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

@chenrui333
Copy link
Author

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
Copy link
Member

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

@bitclick
Copy link

bitclick commented Sep 3, 2024

this has become somewhat urgent, given that the previous release seems to have stopped working entirely, see #1322

@bitclick
Copy link

bitclick commented Sep 5, 2024

There is currently no working release. Maybe you could provide snapshot binaries.

I understand that the new version is not yet ready for a release. In the current situation, many people are trying to compile dev over and over again.. I am sure, many more would be very grateful 🙂

@roderickvd
Copy link
Member

Yes, we are going to do final touch-up and review of #1309 and then get 0.5 out of the door.

Depending on what @kingosticks can muster up coming days, and when I can find some spare time, target is "soon". As in, I'd love to do it this weekend or some upcoming evening but life is busy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants