Posts related to the MusicBrainz encyclopedia in general: community, data, client, server, etc.
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!
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!
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
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. 😉
We’re working hard to get to the Release Candidate 1 release for NGS. We’ve got lots of code reviews in progress, lots of code being committed and a lot of activity all working towards shipping NGS.
However, as we’re working an exposing new features we’re still getting a number of new bugs submitted that expose other issues that we need to address. This is the problem with porting a very large old codebase — we need to simply slog through it and get it done as soon as we can.
With those caveats, I’ll say that I expect the RC1 release to happen somewhere near the end of November. When we get closer and our bug list is converging, I’ll post an actual date for this release. In the meantime, we’re going to put our heads down and get more work done.
Sorry for being vague about this — but I would much rather not slip anymore releases.
I’ve just pushed out a new NGS data dump.
We’re finishing up work on the migration scripts and we’re hoping to finalize the last schema change for NGS next week. After that the NGS schema will be officially frozen in anticipation of the release. After this change I will update the data on the test server and restart the replication feed for one (hopefully) last time.
Stay tuned for more updates!
I’m sorry to say that we’re running a bit behind in bringing you MusicBrainz NGS Beta 3, but we’ve finally managed it!
I am, however, proud to say that we’ve made incredible progress in the last few weeks. Not only are Warp and Acid2 rounding out our features nicely, but with Nikki and Navap backing us up we’ve found/fixed a ton of problems and made countless improvements to the look of the new site. While at times it seems that we’re working on Duke Nukem NGS that seems to never get finished, it is days like today that make me very happy with what we are going to deliver when NGS ships. We’re making sure that the software we deliver at the end of this massive process is solid and will make our users happy. In that sense I am very happy that our users and customers are giving us the time to finish this project properly.
Enough waxing poetic — now for the meaty details of this release! Take a look at the massive change log that shows all the issues we’ve tackled since beta 2. The beta 3 release is available for your testing pleasure on our test server. If you’ve not logged into the test server before, use your normal password from the MB site — the data on test is a little bit old so if your password doesn’t work, try using one that you’ve used a couple of months ago.
This release is solid enough for people to come in and have a serious play. Please come test your favorite features and if you find bugs, please report them to Jira, our bug tracking system. (click on Create Issue in the upper right hand corner). We’ve fixed a ton of bugs already and we’re not afraid to have you report new ones! Beta 3 adds more features and improves many other features, but it is still not feature complete. Our next release, Release Candidate 1 will be feature complete — I hope to set timeframe for this release within a couple of weeks.
And now for some quick notes on areas of NGS that we’ve been focusing on:
Thank you to everyone who has worked on this release! Things have been a little stressful the past few days as we tried to push as many things out the door as possible, but the results have been quite worthwhile. Now it is time to relax a little before we start charging towards our Release Candidate 1 release. Thanks everyone!
UPDATE: I added a note about the RDFa support.
After our weekly meeting we’ve decided that we’re going to release Beta 3 this wednesday. Stay tuned for more info on Wednesday!
What would a deadline be without a delay? Sadly, we felt that we were not quite ready to unleash beta 3 today. Rather than unleashing software that isn’t ready, we’re opting to delay beta 3.
We’re taking a look at where we stand and we hope to be able to finish it for next week. I’ll post about an update hopefully tomorrow.
After a 3 hour bug triage session with the team we’ve managed to sort out the bugs and come up with a schedule for the next release. After looking at the number of bugs for us to tackle before the release, we felt that we really needed to have one more beta release before we are ready to call it a release candidate. Given that, we’re going to do yet one more more beta release on 7 September.
I know, another beta release? Yes, we’re sorry that this is stretching out longer than it should have, but we’re dedicated to releasing the software when its ready and not before. We’ve done our best to cut out unnecessary features, but we still have about 8 weeks of work to do. Fortunately, both Oliver and Warp are now working full time and and fully focused on this release. Re-writing a 10 year old codebase isn’t an easy thing to do and so far it looks like NGS will become stable before perl6 does. 🙂
The release candidate 1 will be 100% feature complete with no new features or tweaks being added. All we will do to the release candidate is fix bugs! For this reason we are not creating an NGS release milestone in Jira. That way, no one can postpone any tickets into the final release. 🙂
To see what we have planned for the upcoming releases, please take a look at the bug list for beta 3 and the bug list for release candidate 1. Currently we expect release candidate 1 (and hopefully only 1) about 4 weeks after beta 3. We hope to then release NGS onto the servers 2-4 weeks after that.