How do you keep your tools updated?

Question

I don't know why, but I always seem to neglect updating my tools, even when they nag me. I think I'm encountering two problems. First, for the tools that tell me there is a new version, I don't want to update at the moment because I'm using the tool, so I put it off, and then forget to update it later. Second, the tool doesn't tell me and I don't visit the tool's site enough, so unless someone tells me there's a new version, I don't know right away.

What can I do to keep all of my tools up-to-date? What do you do (at home or work) to fight these problems?

---

I'm personally interested on a Windows machine, but if you use a different OS, still feel free to share your techniques. I might still find a way to use them.

Answer 1

apt-get update && apt-get dist-upgrade

Package managers FTW!

Seriously though, not sure that there is an easy way. Maybe all the tools you use have RSS feeds on their websites you can subscribe to..

---

Edit: Just got the additional info that you're stuck on Windows. So ignore the Debian GNU/Linux joke.

Answer 2

One approach is to just wait until you have a problem with the software that is impeding your ability to accomplish your task, and check for relevant updates at that time.

Answer 3

Personally, I keep all my development tools (compilers, decompilers, doc searchers, etc.) in a Subversion repository. That way all my employees and I are using the same versions and it's easy to roll out updates and to setup new dev machines.

That said, this works for well-behaved tools. Other tools (like Visual Studio) that require laborious installations don't take kindly to such methods. Eclipse works great in this scenario.

Answer 4

When I see an update notice from the app I will just go and download the update and then install it when it's convenient.

I also subscribe to the email list for the apps that I use. I have a special email account for that which I check every so often to see if there are updates and go download the updates I need.

And the last solution is http://www.iusethis.com. For Macs, there is an app that monitors updates to that site and based on the version of the app you have installed, it will tell you that you have an update.

Answer 5

On windows I just do the 'right' thing and reinstall the OS ever 4-6 months and download the latest version on reinstall.

On my servers(debian) its just apt-get update, apt-get upgrade, apt-get dist-upgrade

Answer 6

I run the FileHippo Update Checker once a week or so to update all my free software, and pretty much everything else gets updated via Microsoft Update.

Answer 7

If the tool has a blog, most do, subscribe to their rss feed and you'll be kept up to speed on updates and news.

Answer 8

Generally I don't believe in updating tools except as necessary. Tools should be stable enough that there are no egregious bugs that impede progress. The best time to upgrade is between (major) releases of your own software. This allows you the most time to get used to any new bugs, new API's and other issues that may arise without affecting release dates.

Answer 9

I keep most of the tools that we need for building in Subversion and import them into the various project trees using svn:externals. That way, when I update NUnit, for argument sake, then NUnit is updated for all my projects.

This technique also gives me the flexibility to keep some projects on the old version by pinning the revision number in the svn:externals definition.

For tools that do not end up in Subversion, I usually just subscribe to the news blog of the tool and usually release announcements are posted to these blogs.