I always wanted to revive this column but never found a controversial edit that was interesting enough / didn’t have too much flame notes.
I always wanted to revive this column but never found a controversial edit that was interesting enough / didn’t have too much flame notes. So, here we go:
What’s it about? Well, in short: if an artist releases a song on their website that is likely or said to appear on a release in the future, then is this a legal non-album track or not? Of course it’s also possible that it will definitely appear on a release but in another version.
So, shall we wait until the release is out and then only add it as a NAT if it’s a different version or should we just add it and later delete it if necessary (the guidelines state this)?
The TRM server hardware has been giving us some issues in the last week. We’re having to reboot the TRM server a lot more frequently than I care for, so I will take the TRM server down tomorrow and have a look to see what the issue might be.
The TRM server will be offline for about 1-2 hours tomorrow Wednesday August 23rd, at Noon PST/2000 BST/2100 CEST.
UPDATE: The outage is now over — I could not find any problems with the server, so the random lock-ups go unexplained. 😦
Technorati Tags: outage, service
The main server was just updated with the latest changes.
Technorati Tags: release, server
After passing on the release last weekend, I think we’re ready to try again. This is the last call for bugs for this release! If you find a serious bug, please enter it into trac and I’ll see about getting it fixed. Please don’t enter any enhancements requests for this release — I’m only fixing bugs at this point and will do no enhancements right now.
The bug fix update release is scheduled for this Sunday. Go test on the staging server and report bugs or look at the list of closed bugs.
Technorati Tags: musicbrainz, release
Over the past few weeks I’ve taken our venerable first server zim and given him a bit of an overhaul. A new motherboard, with 2GBs of RAM and a RAID SATA controller have given Zim a new lease on life as our test server. Now that the test server is no longer at my house, I can stop paying for the expensive net connection with the static IPs. Yay!
The staging server is currently called zim2.musicbrainz.org, but this should be fixed some time tomorrow.
I would like to give a big-fat thanks to Cliff Skolnick, Apache contributor and the leading force behing RightRound. Cliff is hosting our new staging server in his personal hosting setup as a favor to MusicBrainz. Thanks Cliff and the team at RightRound — we appreciate your support!
Technorati Tags: hardware, hosting, musicbrainz
As many of you may have noticed, we’ve had a number of conflicts surrounding the development of the MusicBrainz server source code. Open source developers must work to foster the community of their projects and work towards creating a consensus towards new/improved features.
After an increasing number of conflicts with the community Stefan was warned that his actions as a developer were not acceptable. After countless emails and a number of Skype calls I warned Stefan that the next time he participated in an escalation with one of the community members that I would remove his developer privileges.
Today another one of these escalations took place and I removed Stefan’s developer privileges.
As of right now, I will assume all duties of the MusicBrainz server developer. I will fix any remaining bugs, settle remaining conflicts and work to get the next bug update done as soon as possible. Fortunately now that I can devote all my time to MusicBrainz, I will have more time to devote to getting new server features coded.
With a heavy heart,
Technorati Tags: communities, musicbrainz
Too many bugs have rolled into allow us to to a bug fix update this weekend. Given the update fiasco from last time, we’re going to wait until the issues settle and these bugs are addressed.
I know a lot of people are anxious to get this bug fix release out. If you are one of those people, make sure you get your bug reports in ASAP. Unloading a wad of bug reports that should’ve been raised weeks ago within 48 hours of a planned release will only hamstring the release process. If you’re one of the people who is anxious about getting bug fixes out, please enter your concerns now and not 2 days before the next attempted release date.
We’ll shoot for next Sunday as a the next update time.
Technorati Tags: musicbrainz