Mopidy 4.0 is just around the corner. I’ve released 4.0.0rc1 and 4.0.0rc2 today, and will shortly (on the scale of hours to days) release 4.0.0 final if I don’t find any other issues.
In other words, it is a good time to give it a spin and try it out with your favorite extensions!
Are there DEB packages available or should one use the sources to test?
There’s only the PyPI release or Git.
I’m kind of hoping that other Debian Developers will pick up most of the maintenance of the Debian packages going forward. Since moving them from a dedicated Mopidy team into the Debian Python Team, that has so far worked out great, with lots of modernizations and improvements done to the packages.
By not mentally connecting making a Mopidy release to having to update Debian packages too, I’m hoping to become better at releasing improvements continuously, at the cost of letting the Debian packages only catch up eventually.
Ok, thank you for your quick answer and all the great work!
I’ll switch to the PyPI packages and test v4.0.0rc2
Should not release candidate have their documentation visible on ReadTheDocs? What do you recommend to read install instructions for a release candidate?
EDIT: Reading from sources is quite comfortable.
On Read the Docs stable is the latest stable release, while latest tracks the main branch, so everything that has been merged into main is visible in the latest docs.
You can find the combined changelog for all the changes in 4.0 in
the latest changelog.
For a bit more details about what is in each alpha or release candidate, GitHub Releases has a bit more details.
It was a laborious day: I first had to upgrade from Bookworm to Trixie, fight pipewire, and finally switched from system user to a user running Mopidy in a virtual environment.
Mopidy-Local (v4.0.0a6) work has expected.
All other extensions I use are broken (EDIT: most is fixed!):
pkg_ressources package;The playlists created with the m3u extension don’t load anymore.
I’ll have a look on the work to be done to migrate Mopidy-Listenbrainz.
EDIT : See Support for Mopidy 4.0 · Issue #204 · orontee/argos · GitHub where a fix is provided.
Browsing directories with Argos doesn’t work anymore: Directories containing tracks appear empty, as if the returned tracks weren’t considered valid by Argos (but no particular log). Same observation with Somafm library: appears empty.
A fix for Mopidy-Listenbrainz is available from GitHub - orontee/mopidy-listenbrainz at support-4.0.0 · GitHub ; I’ll submit a PR to upstream once 4.0.0 will be released.
Same for Mopidy-Somafm: GitHub - orontee/mopidy-somafm at support-v4.0.0 · GitHub . But still not validated.
Mopidy v4.0.0a6 is an older alpha version. The current release candidate is 4.0.0rc2: History
The latest releases of Mopidy-InternetArchive and Mopidy-Podcast should work fine with RC2.