MetaBrainz Foundation Community Blog
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!
After much scheduling and getting our ducks in a row, we’re pleased to announce the final beta release of NGS on May 24th! This is one year after our last release, so this date is a little bitter/sweet for us. I had hoped to get this release out before then, but the team is making sure we’re getting this release right, and there are a ton of difficult things to get right.
And the tentative release date for NGS is going to be in July. No promises on a firm date yet.
Hi folks, just a quick announcement – our main web server frontend had some minor problems earlier, but we’ve since sorted it out. It seems to have only effected the web frontend, and not other services such as the web service.
We’re back up now though!
The VMWare image has been updated for the 2009-05-24 server release. The previous image was getting old and updating steps have been reported not easy.
The new image has been upgraded to Debian 5.0, includes a more recent Linux kernel and uses PosgreSQL 8.3 (the required version to work on NGS).
To download and play with the new image, read our VirtualMusicBrainzServer wiki page!
I just pushed a set of fixes to the main servers. To see what has changed, check out the recently closed bug list. More bug fixes will come later this week.
We’ve just finished rolling out our latest release to support Release Groups, ISRCs and CD Stub searching!
For all the details on this release, check out the release notes.
I would like to thank Luks, Dave Evans, Navap, Outsidecontext, Voiceinsideyou, Murdos, Pronik, Prodoc and everyone else who has helped put this release together! Thank you for all your hard work!
P.S. Happy Birthday to Matt Wood!
Welcome all Lifehacker users!
Unfortunately you picked a bad day to come inundate MusicBrainz, because today is our next server update. This will start very soon, within about half an hour of me posting this entry. We expect to be down for at least 30 minutes today.
Sorry for the inconvenience!
I just rolled out a few bug fixes and enhancements to the main server:
Many thanks to Luks, Nikki, Brianfreud and Navap for helping with these fixes/improvements.
This week MusicBrainz experienced problems while trying to deliver mail to gmail.com / googlemail.com. The problem is now fixed, but regrettably this means that some messages that MusicBrainz should have sent are now lost.
This week MusicBrainz experienced problems while trying to deliver mail to gmail.com / googlemail.com. The problems started on Tuesday morning (UK time). On Friday morning the problem was identified as a broken DNS server, which was then fixed, thus resolving the problem.
Regrettably this means that some messages that MusicBrainz should have sent are now lost. The number of lost messages is approximately:
Please accept our apologies for this error.
I come bringing good news! With the latest version of the server now out in the wild, we’re ready to move on to the next stage of MusicBrainz development. But first a quick refresher…
You may recall, many moons ago I (Oliver Charles aka aCiD2) began work on moving the mb_server codebase from our own in-house framework, to the tried and tested Catalyst framework – along with separating out the HTML into separate Template Toolkit templates. Well, after what seems like an age, it’s finally got to the time where I can start getting some critical feedback from the most important people – you!
As from now, test.musicbrainz.org is now running the development branch of this work. It’s important to realise that this new codebase currently has no javascript support. This decision was made because it’s very important we get the website fully functional, and then add bells and whistles on later. We’re starting from a mostly clean slate, so there’s a lot of chance of things breaking, and JavaScript was likely to be just one more headache.
Oh, and I’ve never deployed a server like this before, so please bare with me while I work out any problems running the server. I’m going to London tomorrow and coming back Saturday evening (slightly bad timing, I’m aware) – but I’ll do my best to check any messages that come my way!
However, before you jump straight in and overload us with work – I’d like to lay down some guidelines for providing us with feedback. This will (hopefully) ensure that we can see to these bugs as fast as possible.
Where to report:
Standard practice- report at our bugtracker – bugs.musicbrainz.org
What should you report?
The most important things to report are actions that cause errors to occur, invalid behaviour or features that are simply not available, but are from the main server. You should also report typos and other visual problems – but I will be encouraging people to help fix these themselves (more on this later!).
What information should you provide?
The most critical information is that you can provide us with as much context as possible. Please let us know:
The last point relates somewhat to Catalyst. Catalyst features improved error handling and can provide us with a stack trace. You should try and include this stack trace, and the errors at the top. Chances are, we’ll be able to reproduce this from the information you provide – but if not, the stack trace gives us one more pointer to where the problem is 🙂
How should you organise the report?
Generally speaking, just try to fill in as many of the fields as possible. I’ll be reading every single report that comes in, and re-filing it myself where necessary. Ideally, set the component to ‘MusicBrainz’, the milestone to ‘Server: TemplateToolkit’ and assign the bug to me 🙂
So…