The 0.10.3 version of the tagger fixes a number of bugs and provides new options for configuring the file names.

This bug fix version fixes problems in the id3v2 tags generated by the
0.10.2 version. This version also supports logging, removing id3v2 tags
from ogg files, sports new toolbar icons, shows special too short
and silence trms.

With the increased load on the TRM signature server tagging clients may encounter
TRM server busy messages and the tagger now captures those and reminds the user
to donate money to MusicBrainz when the TRM server becomes busy. The tagger also
supports the new %type (album type), %status (album status), %year, $month, %date
(for first release date of the album) and %country (first release country)
variables for the saving tagged files. These values are now also written to
the metadata tags.

Changes mainly of interest to MusicBrainz Users

Bug #874401 has been fixed. This bug meant that when you added
“Various Artist” albums, any sortnames you specified for new artists
were ignored. Now you can specify both the name and sortname as
you create the artist, as you’d expect.

Changes mainly of interest to MusicBrainz Programmers

Web service changes: release dates, and release type and status have been
added to the QuickTrackInfoFromTrackId query. This query uses
the same RDF prepresentation that the GetAlbumFromGlobalId function
returns. This query will be deprecated for the next version of the web
service; the QuickTrackInfoFromTRMId function has also been
deprecated.

Changes mainly of interest to MusicBrainz Server Programmers

We’re switching over to useMemcached for our cacheing
implementation (after a short spell with Cache::SizeAwareFileCache at the
last release). Of course this means you’ll probably want to install
Memcached on your machine if you want to run a MusicBrainz server.

Some obsolete cleanup scripts have been ditched, and “RemoveBadTOCs.pl” has
been completely rewritten (and renamed).

In Discid.pm,_FindFreeDBEntry has been removed – it wasn’t used any more, and if
we had happened to invoke it there was a nasty bug in there waiting to bite,
which would have caused data corruption of the TOC table.