There has been some discussion as to whether future plans for development should be detailed officially, and whilst it’s a difficult one to adhere to, some idea of work in progress and also projected items to tackle would be very useful, especially items the development of which or lack thereof can result in potentially massive numbers of man-hours of re-working files structures, tagging etc, within the customer base.
A prime example is album art. At the moment I have my collection with album art separated off from the folders of music.
Each album of music, flacs, or DSF, etc, is in one named folder with the art in a parallel folder in the same folder level and with the same name as the music folder but with a suffix “ART”. This avoids unnecessary duplication in case there’s a double album, and also avoids filling up the music folder with art which is not very elegant.
Now, with Roon, to get it to read all this lovely info in pictorial form, I need to put the album art in to the folder with the music, so of course, now I’m studiously going back through 1000’s of folders and moving data, deleting ART folders, etc. Thus taking up a lot of time, which of course is a labour of love in our OCD world.
But imagine in next build that Roon allows for some kind of logic to add the album art from a parallel folder or other system to scavenge art in an even better way, then it renders all that work null and void or worse still will set us off on another path to meet the criteria of the new system which has been implemented.
Even if there’s no timescale given, at least we can say to ourselves, “ok this is on the cards, so maybe Ill hold fire with this massive undertaking my side and see how things go for the next year…”
There are similar issues with file tagging best practices and how Roon accomodates and displays data based on tags. And probably a host of other areas which would benefit from a fluid software roadmap.
Just sayin… 
Right… I’m off back to my album art processing…
