Does RoadShow need daily caring? I mean, I is mature project which is presumably out of beta stages since many years. If you were going to develop completely new features it could be another bounty project again.
When you assume responsibility for software of your creation, you are supposed to be able to answer questions regarding its performance, its limitations and give hints on working around them. That's not counting in collecting the information required for fixing bugs or adding new features.
The first part of "caring" is in helping the product to reach its audience, and make the audience care about the product. I can understand that a bounty would neatly fit the first part of such a process. Get the thing out the door and into the hands of the users. That would cover the first act.
The second part of "caring" is the tedious bit. Now that you've slain the dragon, so to speak, the villagers will start to complain about the damage the animal did to their property and expect you, the guy who slew the dragon, to be sympathetic to their pleads. After all, you did the big thing, everybody was happy, and now you're going to get dragged back into the daily business, which is not very exciting. I can't see a bounty taking care of the bug fixes and the enhancements. It may sound neat when you think about it, but once reality settles back in, you'll find that chasing after bugs and preparing for the next iteration of the product is not as exciting and motivating as things were when you prepped for the first act of the effort. There may be a reward in the distant future, but as experience shows, that distant reward can be poisonous for software development.
I dont expect Amiga software is going to sell more than 50-100 copies in total these days... most of sales happen when product is released and then stagnate to very low numbers. In few months you have saturated entire Amiga market and it is not growing.
It is your choice of course but in my opinion with limited market bounty generates more pleasure to both users and developer.
You're talking about the software equivalent of a one-night-stand. Wham, bang, thank you ma'am. I'm not that kind of guy. If it's software, your responsibilities will last, and last longer than you may have expected when you made worst case predictions. And the best thing to make them last is to stretch out the rewards aspect of development. So, to put it into words, I do not believe in bounties to provide for a lasting development process.