We are planning to (finally) release Picard 1.4 at the start of February.
There were a lot of changes since 1.3.2, and even more recently (thanks to GCI), so we need testers to identify annoying issues before the release. You can get the current dev version from https://picard.musicbrainz.org/downloads/
1.4dev is pretty stable, but you have to know config format changed so it is not very easy to go back to 1.3.2 after installing 1.4 (you can always clear config though). The upgrade from 1.3.2 to 1.4dev should go smoothly (thanks to upgrade hooks feature).
Also, since https://github.com/metabrainz/picard/pull/456, Picard is using ini format to store configuration on all platforms (before the config was stored either in various format files or registry, depending on platform).
Many new features and bug fixes were implemented, and we are still working on few ones.
So, if you have time and you didnāt already, upgrade to 1.4dev, and report any issue through https://tickets.metabrainz.org/
Iām sorry, but I canāt. I had a working OS X build machine, but I donāt remember how it was setup. It was running 10.6 and I had to upgrade to build something else on it. I only managed to upgrade to 10.7 though (the Mac Mini I was running it on is very old), which is not supported by a lot of things either, so Iām afraid Iāll not be able to do a clean install of PyQt4 on the machine.
Ugraded to the latest available Windows Dev build (1.4.0dev7), and now notice that when enabling the āMove Filesā option, the associated files as defined in the settings are not being moved along with the tracks.
I have the āMove Additional Filesā option selected in Picard, as it was in 1.3.2, which WAS moving additional files correctly.