I follow the example of Rob and I will put here my suggestions about desired bug fixes.
I'll add here in no particular order, just out of the top of my head.
Up to .42 boot process was a matter of maybe less tha a minute, with .43 boot sequence is taking quite a while (not ages, but still a few minutes) to go past the "Startup Networking" step. This happens either in core or in MD, and it's a bit annoying when you have to "wake up" a sleeping MD to watch a movie or listen a song. I guess it may have to do with some recent changes (maybe migration from nfs to cifs), so maybe there's not much improvement margin, but I would anyway consider it as an issue.
My MythTv stopped working after update from .39 to .40. Before that it was working simply great, after that I've also performed fresh install to get rid of the upgrade problems I've been affected but MythTv never came back to work. Probably this Pluto feature is in a transition stage and cannot be cosidered stable. Nevertheless I believe that it may be considered a key feature in a fully integrated automation system, and I think it deserves some additional care.
The system used to add applications in Computing sections is a bit complicate. I never really understood the template concept, as I'm using always the same one (Firefox-bin) and things are working.
In past releases the application list were displayed in a little messy way (i.e the application path instead of the description), now the situation seems OK but the application list is mixed (messy entries with proper ones). This actually is a minor issue, and may be solved by manually deleting and recreating entries in PlutoAdmin. But here comes the annoying issue.
As a side effect of recent windows manager change when opening PlutoAdmin with Firefox on my hybrid, only main pages ca be accessed while popup windows are sent in foreground and cannot be accessed in any way, not even "ALT+TAB-ing".
This makes impossible to fully use PlutoAdmin (on a hybrid) to perform such administration operations (editing computing pops up a window, and subsequentely another window).
As Rob said, I will edit this post adding more suggestion (if any). I may check the new ones with a **, to facilitate reading