mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #1279] request a new release #588
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#588
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @chenrui333 on GitHub (May 7, 2024).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1279
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 commented on GitHub (Jul 25, 2024):
up
@chenrui333 commented on GitHub (Aug 1, 2024):
cc @roderickvd
@roderickvd commented on GitHub (Aug 2, 2024):
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 commented on GitHub (Aug 2, 2024):
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 commented on GitHub (Aug 2, 2024):
(because one requires minimal support, the other requires loads)
@chenrui333 commented on GitHub (Aug 19, 2024):
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 commented on GitHub (Aug 21, 2024):
I'd be up for a release after #1309. My point about depending on you guys remains.
@bitclick commented on GitHub (Sep 3, 2024):
this has become somewhat urgent, given that the previous release seems to have stopped working entirely, see https://github.com/librespot-org/librespot/issues/1322
@bitclick commented on GitHub (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
devover and over again.. I am sure, many more would be very grateful 🙂@roderickvd commented on GitHub (Sep 5, 2024):
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.
@roderickvd commented on GitHub (Oct 15, 2024):
Just released v0.5.0: https://github.com/librespot-org/librespot/releases/tag/v0.5.0 🎉