And yet another edit that caused a little controversy:
The voting is a bit one-sided at the moment but it seems that working practice has outpaced guidelines again. The FeaturingArtistStyle has always been the bone of contention (see SG5DisasterRelief for example) – now the question is if AdvancedRelationships as a mean of crediting of what an artist has actually done on a release (in NextGenerationSchema-talk: “what it is”) are shifting the “feat.” in track titles to a role where it only credits “what it says”, that is when the artist intended to credit guest appearances prominently on the cover.
The con is that the presence or non-presence of “feat.” on covers barely expresses artist intent because it is done by cover designers and mostly the artist doesn’t have a say in the design.
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)?
Picard version 0.7.0 Beta 3 has been just released.
Changes from 0.7.0-beta2:
- support for GNOME and KDE default browser settings, in addition to the BROWSER
environment variable (#1257)
- fixed crashing in Pango (#1256)
- added tport= parameter to the CD lookup URLs (#1328)
- new code for checking user name and password that doesn’t block Picard
when internet connection is down (#1247)
- fixed bug that caused directory selector to become “sticky” after drag&drop
on Windows (#1183)
- support for Windows-compatible file names also on non-Windows systems (#1014)
- and a couple of other minor bug fixes