Category: Development

First NGS Bug Fix Release Now Out

Our first set of bug fixes have now been deployed on our production servers! Please keep the bug reports coming in, we’re aiming to do almost daily releases until we really get things stable. Here are the bugs that are now fixed:

Bug

  • [MBS-1660] – “To be cancelled” edits aren’t highlighted
  • [MBS-1665] – “Artist as credited” gray default must be manually set
  • [MBS-1776] – Seeding releases no longer picking up tracks on ngs.musicbrainz.org
  • [MBS-1888] – Change direction shown for relationships where changing the direction is not possible
  • [MBS-1897] – 500 error in release editor
  • [MBS-1898] – Changing artist {credit} for release and tracks in VA conflicts
  • [MBS-1902] – Internal Server Error trying to edit a Release<->URL relationship
  • [MBS-1912] – Weirdness after editing release labels
  • [MBS-1913] – “Attribute (params) does not pass the type constraint because: Validation failed for ‘HashRef’ with value undef”
  • [MBS-1931] – Beethoven’s Relationships timeout
  • [MBS-1952] – Simultaneous Release edits impossible
  • [MBS-1954] – Medium edit page shows tracklist when it hasn’t been changed
  • [MBS-1959] – Internal server error when trying to relate a recording to a work
  • [MBS-1962] – Cannot cancel edit
  • [MBS-1963] – Release in a remove release label edit doesn’t display
  • [MBS-1967] – Internal Server Error in relate to recordings
  • [MBS-1977] – ModBot complains more
  • [MBS-1980] – ISE when adding standalone recordings for artists not in the DB
  • [MBS-1996] – Setting track durations from TOC returns back to same page
  • [MBS-2002] – “Internal Server Error” when attempting to add release to existing release group
  • [MBS-2003] – Error entering a various artists edit
  • [MBS-2004] – Internal Server Error attaching Discogs URL
  • [MBS-2006] – Internal Server Error submitting add release label edit
  • [MBS-2019] – Release editor > Advanced tracklist mode > Can’t change artist credits of tracks of a release with 5 mediums
  • [MBS-2024] – Voting twice gives odd results
  • [MBS-2089] – Error displaying release label edit
  • [MBS-2090] – Merge artists doesn’t show whether the keep artist credits box is ticked
  • [MBS-2091] – All relationship IDs in the URL cleanup JS are incorrect
  • [MBS-2100] – Removing an {artist} alias is an autoedit for autoeditors
  • [MBS-2105] – Merged artist not being redirected to target artist

Picard 0.14 released

NGS is obviously the release of this week, but Lukáš has today announced the release of Picard 0.14 on the mailing list.

Picard 0.14 should be the last release that doesn’t support the NGS web service. It brings some improvements in handling of network errors, changes the default ID3 version, finally adds support for sorting, prioritizing matches based on release types and fixes a couple of bugs. It is also the first release that has a Mac package available at the release time, many thanks to bitmap for that.

You can download the packages as usually at http://musicbrainz.org/doc/Picard

Changelog:

  • Fixed a problem with network operations hanging after a network error (#5794, #5884)
  • ID3v2.3 with UTF-16 is now the default ID3 version
  • Option to set preferred release types for improved album matching
  • Added support for sorting the album/file lists (#75)
  • Fixed OptimFROG tag reading (#5859)
  • Fixed colors for a white-on-black color scheme (#5846)
  • Added an option to replace non-ASCII punctuation (#5834)
  • Support for writing release group and work IDs, currently unused (#5805)
  • Fixed saving of the release event format tag (#5250)
  • Added support for the language and script tags (#943)
  • Plugins can now use track-track relationships (#5849)
  • Allowed external drives to be visible in the file browser panel on OS X (#5308)

New NGS Virtual Machine available

The promised Virtual Machine for MusicBrainz Next Generation Schema Release Candidate 1+ is now available for download. This virtual machine is setup as a slave and can pull replication data from the test server by running the admin/replication/LoadReplicationChanges from the musicbrainz-server codebase about 10 minutes after every hour.

See our wiki page for details on how to use this VM

Virtual Machine for NGS RC1 available for download

I’ve just finished uploading the Virtual Machine for MusicBrainz Next Generation Schema Release Candidate 1. This virtual machine is setup as a slave and can pull replication data from the test server by running the admin/replication/LoadReplicationChanges from the musicbrainz-server codebase about 10 minutes after every hour.

This is an easy way to jump in and take a look at how NGS and replication in NGS will work! (hint: the replication doesn’t change much)

UPDATE: See our wiki page for details on how to use this VM

Next Generation Schema Release Candidate 1 now available for you!

The MusicBrainz development team has been working hard to reach the RC1 milestone for NGS and we’re proud to announce that we’ve just released RC1 for you to play with! Not only do we have a feature-complete (only small enhancements and bug fixes remain) version of NGS, but we also have a shiny new test server to introduce to the world.

rc1.musicbrainz.org is our new Mac Mini Server based test server. Since our test server doesn’t get used that much, I really wanted to waste less power running a full sized server. And I really wanted to have the test server co-located with the rest of our machines, so we opted to purchase a Mac Mini for this job (a Mini only sucks 10W of power for most of the time, which is great). This new machine will also (and permanently) be reachable as the new test.musicbrainz.org, but the DNS hasn’t propagated yet, so we opted to give the machine a temporary name in honor of its first duties.

Back to RC1: We’ve fixed a ton of bugs and we’ve worked hard to get all the new features in that will be in NGS. From here on out we’re hoping to only fix bugs and do minor enhancements. We do not plan to add new features at this point in time. Our focus is to finish the open bugs and ship NGS as soon as possible. In this release we’ve also included a large batch of usability improvements for the Release Editor, which is getting much closer to being complete.

If you’ve been holding off testing NGS, now is the time for you to jump in. We need a lot more help to test NGS and find all those pesky bugs that still remain. Please play with RC1 and log in with your normal MusicBrainz account credentials. If you find any problems, please report them to our bug tracker. We’re specifically looking at people to test the following:

  • Does the data all display correctly?
  • Have we preserved the editing history sufficiently? Can you find all the edits you’ve made and do they display correctly?
  • Can you make new edits and adjustments to data?

We have a new NGS data dump to go with the RC1 release. Replication has also been turned on for RC1, so if you’re interested in testing the replication, make sure you have the latest code from git, import the data dump and then run admin/LoadReplicationChanges 10 minutes after the hour to get updates for RC1. I hope to release a new virtual machine tomorrow that will allow people to test the replication on their own turf — but I’m not quite ready to promise this yet.

Thanks to everyone who helped work on this release!

MusicBrainz NGS RC1 release: A quick update

After a great day of teamwork in preparing for today’s RC1 release it was the database that wouldn’t play along. Our code is ready, but we’re hitting glitches on the database on our new test server.

We’re now waiting for a new clean migration of the data which takes several hours, so we need to postpone the RC1 release for a few hours. 🙁

We’re working hard to get RC1 out ASAP — stay tuned!

Next Generation Schema virtual machine available for download

Using Virtual Box I’ve created a virtual machine that contains a complete NGS installation. This installation also has the latest NGS data (without the edits) loaded in it.

If you’re interested in playing with NGS on your own machine, but don’t want to go through the long setup process, this virtual machine is for you!

To play with this virtual machine on your Windows, Linux or Mac machine, read our wiki page!

Next Generation Schema Release Candidate 1: Monday January 17th

As of today we can finally see the light at the end of the tunnel! We feel confident that we can finish all new features (and most improvements as listed in jira) by January 17th. Once we reach RC1 we’re going to freeze the features for NGS and only work to fix bugs in our codebase.

That said, we hope to release NGS onto the main servers sometime in February.

Its been a very long road to NGS, but it is finally tangibly close. I’m getting excited!

Next Generation public schema frozen & new data dump available

Hello and Happy New Year!

Very late last year we finally hit a milestone we’ve been working towards for quite some time: Freezing the public NGS schema!

The public schema refers to the collection of tables that will be replicated in NGS. See below for a complete list of all those tables. However, we may make small changes to some of the tables in NGS that are not replicated. This should not affect anyone, unless you are actively hacking on the MusicBrainz Server code.

Also, we have a new data dump for this frozen schema available for anyone who would like to play with it. This data dump will cleanly import into the current version of the server source code in git.

All the tables that will be replicated for NGS:

annotation, artist, artist_alias, artist_annotation, artist_meta, artist_tag, artist_credit, artist_credit_name, artist_gid_redirect, artist_name, artist_type, cdtoc, clientversion, country, gender, isrc, l_artist_artist, l_artist_label, l_artist_recording, l_artist_release, l_artist_release_group, l_artist_url, l_artist_work, l_label_label, l_label_recording, l_label_release, l_label_release_group, l_label_url, l_label_work, l_recording_recording, l_recording_release, l_recording_release_group, l_recording_url, l_recording_work, l_release_release, l_release_release_group, l_release_url, l_release_work, l_release_group_release_group, l_release_group_url, l_release_group_work, l_url_url, l_url_work, l_work_work, label, label_alias, label_annotation, label_meta, label_gid_redirect, label_name, label_tag, label_type, language, link, link_attribute, link_attribute_type, link_type, link_type_attribute_type, medium, medium_cdtoc, medium_format, puid, recording, recording_annotation, recording_meta, recording_gid_redirect, recording_puid, recording_tag, release, release_annotation, release_gid_redirect, release_meta, release_label, release_packaging, release_status, release_group, release_group_annotation, release_group_gid_redirect, release_group_meta, release_group_tag, release_group_type, release_name, replication_control, script, script_language, tag, tag_relation, track, track_name, tracklist, tracklist_index, url, work, work_annotation, work_gid_redirect, work_meta, work_name, work_tag, work_type

NGS Developers: Schema changes pushed to master

Ollie and I have been working on a bunch of schema changes to make things more consistent and to add more time stamps to the database. We’ve included other data migration patches from Luks and Murdos as well.

All of these changes have been pushed to the master branch on our git repository. If you pull this branch from our repo, you must reload your data with this fresh NGS snapshot!

On monday we will discuss if we can call our core schema frozen yet. Let’s hope so. 😉