Murdos recently added a new report that highlights releases that have disc ids that will be discarded during the NGS data migration phase because the data is not conclusive enough to be reliably migrated. If you have some time, please help us review this data so we can save as much information when we switch over to NGS.
Thanks for creating that report Murdos!
(After fixing one buggy dataset, we have a couple of confirmations that the updated data set is ready to go.)
We have a new NGS dataset available — this data set still has a couple of migration bugs for ARs. The “RecordingA is cover of RecordingB” relationships are borked, but the rest of the data looks to be OK.
This new data also contains one very minor schema change: In the artist_credit_name table, the join_phrase column went from VARCHAR(32) to TEXT, to allow longer join phrases. This shouldn’t really affect anyone, but it is something to be aware of if you’re expecting a VARCHAR(32).
We’re going to work on fixing this bug and then we will put out a new data set and start replication off the new servers. In the mean time, feel free to play with the new data.
I’ve also uploaded a new NGS Virtual Machine — for details on how to use this virtual machine, please see the wiki page for the virtual machine.
UPDATE 1: Fixed the dataset and updated the link.
UPDATE 2: Added a note about the schema change.
I’m pleased to announce that we’re finally confident enough with the NGS codebase that we’re ready to commit to a release date: May 16th! There are a tremendous number of things that we still need to finish, but we’re working hard to meet this deadline.
Two weeks prior to the deadline we will begin the process to prepare our users for the switchover. We expect to have about a two week period where we are going to discourage new edits and encourage people to vote on existing edits. We anticipate not allowing any new edits to be submitted by May 9th and we hope to encourage the community to help us review all pending edits in the last week. It would be nice to not have any open edits before we begin the migration to NGS, since we will need to close any open edits at that time. All of these dates are still in flux — we will have a complete migration schedule on May 2nd.
Tomorrow we will be releasing new NGS data, start NGS replication over and hopefully also have a new NGS Virtual Machine for you to download. Stay tuned!
Update: We had previously agreed on a 7 days no-new-edit timeframe; this post now reflects this.
Music Hack Day comes to San Francisco again!
I’m planning on attending and working on some sort of hack that uses MusicBrainz — would you like to join? If so, drop me a line and register for the event using the link above!