As promised, here are some release notes for today’s monumental NGS release.
We’ll post more information on the release, including how to setup slave servers, tomorrow after we’ve had some more sleep.
Category: MusicBrainz
Posts related to the MusicBrainz encyclopedia in general: community, data, client, server, etc.
NGS is live!
We’ve made it! NGS is live! Thanks to everyone who worked on this massive project!
Release notes and instructions for updating mirror servers will be coming soon.
NGS Release time!
We’ve fixed enough bugs, done enough testing and we’re finally happy that we can switch over to NGS:
We’re going live at 18:30 BST! (17:30UTC, 19:30 CEST, 10:30PDT)
NGS: We're fixing bugs
As soon as we let people lose on the final test server with live data, people started finding lots more bugs. Which means that the final switchover will be delayed for a while longer.
But, the NGS data is live and replication packets for the NGS data are flowing. I’ll post instructions on how to tap into this feed later today.
UPDATE: Please be careful with your edits — we plan to keep this data!. Unless some data corruption bug is discovered, we’re going to do our best to keep this data. Please keep this in mind as you edit on this server.
NGS migration is complete
We’re currently doing the last round of sanity checking to make sure we’ve not screwed anything up. Come help us test!
NOTE: This is our release candidate data set — please be careful what you edit. We’re strongly hoping to release with this data set!
If all goes well, expect us to go live at 9am BST on Tuesday 17 May!
NGS Migration is in progress
We’re currently at 7 million edits migrated. We still have a lot of things to take care of, but we’re hoping to let people start playing with the migrated data at about 2:00am BST. We hope to go live at 9:00am BST.
See our updated schedule and maybe follow our updates on twitter.
We’re excited and we hope that you are too!
NGS release update
We had to fix some last minute migration issues and are running a test migration right now. If everything turns out well, we’ll be 8 hours behind schedule.
And after being more than a year late, what is 8 hours (or so…)?
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)
The no-edit phase has been pushed back to May 12
The count of open edits has been dropping nicely and we’ve decided to push the no-edit date back to May 12. We could’ve done the 13th, but Friday the 13th didn’t seem like a good idea for this. 🙂
For more information on this, please read our preparing for NGS guide.
New Web Service policy for NGS
Once we move to NGS on May 16th, we’re going to require each application that makes requests to our web service to have a proper User-Agent header string. The User-Agent string needs to identify the application and the version of the application that is making the request; having a generic User-Agent string like “Java/1.6.0_24” or “PHP/5.3.4” does not allow us to properly identify the application making the requests.
IMPORTANT: 6 Months after we release NGS (Nov 16th) we’re going to start blocking common generic User-Agents strings, so please make sure that you send us a proper User-Agent header as part of your request.