It’s a lot to get through, but over time, the critical issues should gradually rise to the top, and our core developers can help solve these as quickly as possible. Happy voting, and thanks for all your help so far!
It seems that there wasn’t nearly enough consensus about the schema change release as I had expected. We’re going to skip all of the tickets, with the exception of the MBS-3693 ticket.
One of the issues raised at the last summit was that our customers could use more time to prepare for schema change releases, since they require engineering effort on their part. In an effort to meet our customer’s needs we’re going to a set schedule for schema change releases. Going forward we’re going to have two schema change releases per year: On or about 15 May and on or about 15 October.
We’ve picked these two dates as dates that have the least amount of impact from holidays and people taking holidays. Most companies have normal working schedules around these dates, which should allow companies to dedicate the required resources to handle our schema changes.
However, we have one significant change that we need to push out on a more timely basis than May of next year. For that reason we’re going to plan a one-time exception to our new schedule for 12 January 2012. You can see the tickets we’ve scheduled for release in January in this schema change milestone.
We’ve already created release versions in Jira for all of the schema change releases in 2012. As we go through the year we’re going to add tickets to that milestone. Of course, we’re going to make lots of noise as these schema change release dates approach. We’re going to post a list of tickets that will be included no later than a month before the release.
We’ve just updated our search server with the latest changes and bug fixes!
This update to the Search Server finally solves the search for artist “!!!” problem properly, should now be able to find just about any artist, release, etc that contain any crazy character combination. Also you can now search for number of releases in release groups and artists with unknown gender. The code base has now been updated to Lucene 3.4, which was the latest available when these changes were made (its at 3.5 now).
Thanks for your hard work on this Paul!
Bug
[SEARCH-33] – Search needs to find a preposterously bad label name: !"@.*!%
[SEARCH-51] – Searching for certain characters returns no results, even if they’re valid.
[SEARCH-131] – When search for Unknown country it returns <country>UNKNOWN</country> it should return nothing
[SEARCH-134] – Annotation search can’t filter by type for release groups
Improvement
[SEARCH-93] – Update Search Index Code to Lucene 3.4
[SEARCH-119] – Allow artist search for gender:unknown
[SEARCH-124] – Allow searching release groups by # releases
[SEARCH-128] – Make Search Server use mmap by default
Another update has just gone out, a few days later than planned. This is mostly a bug fix and minor improvement release. Sadly, when deploying the update we broke the release editor for anyone who was editing during the server switches – something we didn’t anticipate. Sorry! Here’s what’s changed:
Bug
[MBS-2371] – Can’t type in the basic tracklist editor
[MBS-2785] – Release Editor messes up release artist multi-artist credits
[MBS-3152] – Tracklist duplication with sub-second track duration differences
[MBS-3428] – If seed new release with track artist ids it doesnt properly resolve the artist ids
[MBS-3471] – Wrong display of RG in the Edit Note tab of the RE
[MBS-3498] – Editing tracklists on any release which has been through an artist split fails.
[MBS-3601] – Incorrect "Artist as credited" displayed and impossible to edit track artist in release editor
[MBS-3804] – Entering "Edit barcodes" edit should not be possible if nothing is being changed
[MBS-3808] – Internal server error searching for edits
[MBS-3813] – Release editor gets stuck on tracklist tab saying there are errors when there are none
In an effort to bring the community into our development process more, I (ocharles) have built a new little application to help the MusicBrainz community decide exactly what we should focus on. I present to you, the Scheduling Game!
The Scheduling Game
The idea behind this little application is to let the community quickly scan through open issues and decide when they believe they should be fixed. Each editor is presented with 3 options:
Within 3 months. This ticket must absolutely be fixed within 3 months from now.
Within 12 months. This ticket should be fixed within a year from now. This means the ticket should be fixed within the year, but is not critical for the next 3 months
Unscheduled. This issue is not pressing and can be fixed much later.
Later, when issues have been voted on by enough people, the developers will try and decide how to schedule work to best fit the needs of the community.
A few disclaimers… Firstly, this is just an experiment! We don’t know how well it will work, though initial testing has shown it to already be quite useful. Secondly, it’s not really much of a game, but I wanted to give it a cute name (I know how picky everyone can be!). Currently only a subset of open tickets are available for voting on – specifically tickets in the “NGS + 1” and “Post NGS” milestones on JIRA, as these milestones are in need of a sorting.
The scheduling game is currently live on my server at http://scheduling.ocharles.org.uk/. You can have a look at the current (anonymous) votes at http://scheduling.ocharles.org.uk/results. If you have any questions or comments, you can reach me in IRC as ocharles or email oliver@musicbrainz.org. Happy voting!
A few days behind on this one, but we’ve got this release out. This release has one controversial change, which I want to discuss in this blog post.
Displaying Relationships on Release Pages
A lot of people want this, and we’ve shipped something that adds this functionality. However, a lot of people think this is too verbose, and to a point I agree – there’s a lot of information there that can be displayed better. However, work on this issue has been on and off for almost the past 2 years. We’ve got a solution here that while far from ideal will get this ball rolling.
This is an unpopular move on my half, but I’m asking users to please try and bear with us until the next release (scheduled in for 5th December), which is just over a week away. Hopefully having this fairly messy display so open will raise enough discussion on how exactly to move forward. If you really must see it gone, you can use AdBlock or user styles in your browser to hide the dl.ars element.
Changes in this Release
[MBS-2067] – CDStub not displayed in the "Matching CDs" section on CDTOC lookup page
[MBS-3668] – all edits including "Auto-edits" are being tallied as "Accepted" edits in editor profile
It’s been a while, but we’ve finally got a new server release out! This one didn’t go perfectly smoothly, and we had (more, i’m afraid) troubles with the release editor. We’ve got a fix for this out, so editing should be at least as stable as it was before. As always, please do continue to report any bugs you find. Here’s what’s changed:
Bug
[MBS-761] – Release has ASIN but no cover art ("No cover image available.")
[MBS-1169] – Musicbrainz website is missing HTML escaping on user entered data
[MBS-2529] – Orphaned release group and recordings after rejecting or cancelling a release/medium
With the summit arrangements this release has become delayed, but we’re happy to announce that we have just finished releasing this version (live from the summit!). Here’s what’s been fixed in this release:
[MBS-3070] – Release editor cannot be seeded with >99 for array-like elements
[MBS-3223] – Work relationships not available in web service recording requests
[MBS-3336] – NGS /ws/1 doesn’t include some relationships
[MBS-3350] – ws/2 browsing release by track artist
[MBS-3372] – Add relationship not linking to the URL entity
[MBS-3442] – WS/2: Can’t browse work by artist (ws/2/work?artist=MBID)
[MBS-3456] – Selecting recording from search results in work "Relate to…" doesn’t close results
[MBS-3463] – Remove ISRC edits are not shown pending on recording page
[MBS-3477] – Crash when trying to edit a release to create a new release group
[MBS-3483] – Release editor > Importing a Various Artists CDStub doesn’t import track artists
[MBS-3509] – Change release group via release editor doesn’t show up in edit history / open edits of target release group
[MBS-3523] – Entity not being selected for relationship
[MBS-3528] – Internal Server Error – Couldn’t render template "undef error – Can’t call method "value" on an undefined value at /usr/local/share/perl/5.10.1/HTML/FormHandler/Field.pm line 89. "
[MBS-3564] – Cover arts from ozon.ru are not diplayed
[MBS-3570] – change direction not working when no relationship type was selected first.
[MBS-3573] – Got Internal Server Error while updating info for ‘Mob Hits [Disc 2]’
[MBS-3577] – Release editor converts unicode characters to HTML quotations
[MBS-3584] – amazon.es is not recognized as ASIN in "Add URL Reference"
[MBS-3591] – Finding some labels in AJAX search is impossible
[MBS-3592] – Artist aliases have extremely low priority when doing a simple search
[MBS-3622] – Internal Server Error during import of freedb release that cannot be found
[MBS-3623] – Edit relationship fails with internal error when attempting to move credits between recordings
[MBS-3625] – The FreeDB page throws an exception if you try and view it when the disc doesn’t exist
[MBS-3521] – Sporadic ISEs when trying to view the editing history of an artist
[MBS-3529] – Uppercase cover art file extension not recognized
[MBS-3530] – "Edit barcodes" edits are not linked to relevant release artists
[MBS-3532] – ISE when editing a relationship to the same as an existing relationship
[MBS-3533] – ISe adding a CD Stub where MB already has the discID
[MBS-3538] – Two redirects for /show/edit/conditions.html
[MBS-3539] – Regression: Instrument search in relationship editor no longer works in Firefox/Opera
[MBS-3546] – ISE when visiting Tag Lookup page without arguments
[MBS-3548] – Admin "adjust flags" panel crashes on form submission
[MBS-3549] – Field validation prevents adding lyrics relationship URL to lyricstatus.com
[MBS-3559] – Searching works gives an internal server error: Caught exception in MusicBrainz::Server::Controller::Search->external "Can’t use string ("backward") as a HASH ref while "strict refs" in use
