Development – Page 6 – MetaBrainz Blog

Picard 2.9.2 released

Picard 2.9.2 is a maintenance release for the recently released Picard 2.9 with fixes for reported issues. In particular this solves an issue where Picard could crash on exit leaving a thread running in the background, which prevented Picard to be started again.

The latest release is available for download on the Picard download page.

The detailed changes for this maintenance release are below. For an overview of the new features since Picard 2.8 please see our detailed release announcement for Picard 2.9 and Picard 2.9.1.

On a special note the Picard website is now also available in Italian. Thanks to salo.rock who did the translation.

Thanks a lot to everyone who gave feedback and reported issues.

MusicBrainz website mirror will require Node.js 20 starting from November 13, 2023

This announcement is uniquely intended for administrators having installed any mirror of MusicBrainz website with manually installed dependencies instead of using the Docker Compose project musicbrainz-docker.

MusicBrainz website is rendered using Node.js whose minimum required version was 16 so far. This version is reaching end-of-life next week according to their Release Working Group. Therefore MusicBrainz Server will switch to the active LTS Node.js 18 for a transitioning period of two months. It will still support Node.js 16 for previous installations during this period. After that, Node.js 20 will enter its active LTS phase and be required by MusicBrainz website. It has already been used locally in development for a long time, so we don’t expect any major issue when switching mirrors to it.

MusicBrainz Server update, 2023-08-28

On the menu of the day there are some improvements to the editing interface thanks to derat! It’s accompanied with a mesclun of changes (additions, fixes, improvements and updates) related to external links, especially some other databases and new relationship types for art gallery and ticketing. It’s spiced with a pinch of new icons (for collections, genres, and tags) and condiments.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks also to HibiscusKazeneko, Lotheric, Trevor, wonder_al, Xythium, yindesu, and yyoung for having reported bugs and suggested improvements. Thanks to chaban, outsidecontext, RandomMushroom128, and salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-08-28.

Picard 2.9.1 released

Picard 2.9.1 is a maintenance release for the recently released Picard 2.9 with fixes for reported issues and updated translations.
This release contains important fixes for a potential data loss on Windows and several crashes. Windows users are highly recommended to upgrade.
Please see below for details.

The latest release is available for download on the Picard download page.

The detailed changes for this maintenance release are below. For an overview of the new features since Picard 2.8 please see our detailed release announcement for Picard 2.9.

Thanks a lot to everyone who gave feedback and reported issues.

MusicBrainz Server update, 2023-08-07

This is another summer release with no new features, but it contains a fair amount of small bug fixes and improvements, many related to URL handling. The last user account related pages are also converted to React with this update.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to atj, chaban, Cyberskull, darkshyne, derat, Freso, scoobert, Van de Bugger and yindesu for having reported bugs and suggested improvements. Thanks to atj and derat for submitting code patches. And thanks to all others who tested the beta version!

The git tag is v-2023-08-07.

MusicBrainz Server update, 2023-07-10

This release makes a few small changes, including an updated set of basic edit icons that hopefully will be the start of a consistent icon set for MusicBrainz. Additionally, and sadly, opening voting for new editors has caused the creation of way too many sock-puppet accounts, so we have been forced to restrict voting for beginner editors again. Hopefully the two week wait is not too long; we’ll look into ways to improve beginners’ experience without helping bad actors in the future.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to all others who tested the beta version!

The git tag is v-2023-07-10.

MusicBrainz Server update, 2023-06-07

We have a small release this time, slightly delayed because of maintenance work on our servers for the last couple days. The most noticeable changes are probably 68 new locales available for aliases (for example, we can now specify an alias is in Latin language), and a fix to a bug where a small amount of tracks would not be shown in their release’s relationship editor and as such couldn’t have relationships added from that page.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to salo.rock, UltimateRiff and yyoung for having reported bugs and suggested improvements. Thanks to salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-06-07.

MusicBrainz Server update, 2023-05-22

As announced for our schema change release, after a week of beta testing, the ability to modify or remove edit notes is fully delivered in today’s release! A few other unrelated but small improvements and fixes are included too.

As an editor, you are now able to modify or remove your own edit notes if they’re not older than 24 hours and nobody else has replied; you can see the full set of conditions in our edit note documentation. Admins are allowed to modify or remove any edit note from anyone at any time, and have already been using this to remove some spam and inappropriate comments during the beta period.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to ShivamAwasthi for contributing code and to kellnerd for helping with code review. Thanks to chaban, Cyberskull, jesus2099 q_fdb and yurim for having reported bugs and suggested improvements. Thanks to salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-05-22.

MusicBrainz schema change release, 2023-05-15 (with upgrade instructions)

We’re happy to announce the release of our May 2023 schema change today! Thanks to all who were patient during today’s downtime as we released everything to our production servers, and thanks to CatQuest, jesus2099, and yindesu for creating tickets.

This is a fairly small schema change release which mostly removes unused code and improves things behind the scenes. Of the schema change tickets, there are only two that will directly affect users as they browse and edit in MusicBrainz.

The first (MBS-12800) makes it so that cancelled releases are ignored when calculating the first release dates for recordings and release groups; since something that was cancelled was by definition not released, it should not be used as a first release date.

The second (MBS-11312) lays the foundation for a new feature (MBS-4685) that will allow users to edit or delete their edit notes, as long as a set of conditions are met (see the edit note docs for details). Admins will be able to edit or delete any edit notes at any time (MBS-13084), mostly to get rid of spam or offensive content, but also to help any editor who cannot change their note anymore but has an important reason why they need to do so. This feature will be available for testing in our beta server on Tuesday and we expect to release it next week, assuming our beta testers don’t find any too big issue with it by then.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

MusicBrainz Server update, 2023-05-02

In our last version before the May 15 schema change release, we are mostly releasing a fair amount of React conversion work for smaller pages. We’ve also tried to make some error messages more clear and helpful and made a few improvements to ETI guess case, alongside other small bits and pieces.

The most significant change for editors is the standardization of all auto-deletion waiting periods to 48 hours. Until now, most entities would be removed when empty for 24 hours, while unused artist credits would take a full week to go away. This meant removing the last artist credit usage for an otherwise empty artist would lead to an eight days wait for that artist to be automatically deleted; now it will be four. As a reminder, 48 hours is also the minimum time needed for a merge edit to pass. As such, it’s not always faster anymore to let an entity be removed automatically rather than merging – hopefully this will encourage more autoeditors to merge rather than delete!

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to CatQuest, chaban, jesus2099, Lotheric, and rdswift for having reported bugs and suggested improvements. Thanks to okaits#7534 and salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-05-02.