Thanks! Yes, that's more of the mental state I put myself in. :) But I have to say that I have developed a pretty good feel about when something is ready for release.
My program has to run all day. As soon as I release an update, I have to quickly run the old, installed version of my software to get the current update. Then, I make sure it actually starts. Let's say I add something that works great during testing, but crashes with a file access error on startup. That means the user will come back to the computer and see an error. At least if I introduce a bug that doesn't keep the program from loading, it means that I can then release another update later on which the update I just released will catch. That's what I meant. As long as the update doesn't make the program crash when it starts, the program will find any future updates to fix any bug I introduced, seamlessly.
My only comment is the "and don't introduce bugs" statement ... that is a bit of a tough guarantee isn't it? =)