I set up my Drupal site on 1/23/09, so when I started getting dire warnings about an urgent security upgrade a month later, I was both annoyed and concerned. Annoyed at having to do what seemed like a total re-install when I'd just gotten my new site customized the way I wanted it, and concerned about the potential to totally screw up my site in the upgrade process.
Most of the info I found here about how to streamline the process requires the site admin to write scripts or run them, and this won't work for me since I don't know anything about Linux commands and don't have easy access to run scripts against my server anyway.
Furthermore, while I've always been a stickler for maintaining a separate development environment when building or maintaining programs or web applications, with Drupal it seems like more trouble than it's worth since the 'bones' of the site don't tend to change much once you're done installing and customizing your site. All the content of the site (i.e., articles, forum posts, member profile data, etc.) is stored in the site database, and I don't feel I need a 'development' copy of the database because its structure rarely changes, too. I backup regularly, but that's about it.