Many of you are planning to deploy SharePoint SP1, which is a good idea.  There are many, many useful updates and fixes.

For a detailed rundown, make sure you take a peek at this spreadsheet, which lists all of the 2007 Office System SP1 details: http://support.microsoft.com/kb/942390.

I'd also like to give you a few additional tips:

• Install SP1 on a test server to make sure all of your 3rd party and custom web parts and features still work.
• You can't go back. There's no uninstall. Back up everything.
• The farm is down during the upgrade. Plan accordingly.
• For MOSS 2007 servers, you need to install WSS 3.0 SP1 and MOSS 2007 SP1, in that order. At the completion of the WSS 3.0 SP1 installation, you will be prompted to run the SharePoint Products and Technologies Configuration Wizard. DO NOT RUN IT YET. Instead, cancel it and then run the MOSS 2007 SP1 install. Then, manually start the SharePoint Products and Technologies Configuration Wizard.
• If you're installing SP1 on multiple servers, make sure you complete SP1 on all servers in the farm. If some of the servers have SP1 and some don't, your farm won't work.
• After you install SP1, more disk space is required for your query server or index server. If adequate disk space is not available, your query servers will slow down or stop. This issue occurs because the method used to merge indexes has been modified to significantly improve performance and reduce server downtime. However, this change increases the disk space required to perform a master merge. Previously, a maximum of 2 times the physical size of the index was required. The new maximum disk space requirement on a query server or index server is increased to 2.85 times the physical size of the index.
• If you are using the Content Editor Web Part on a MOSS 2007 Web server that offers languages other than the installed language, users will receive a script error when they use the Web Part. You can prevent this issue by installing the Windows SharePoint Services 3.0 Service Pack 1 Language Template Pack.
• You may get an error related to orphaned objects in one of your content databases. SharePoint requires a clean environment going forward. Here's some information on orphans: http://blogs.technet.com/corybu/archive/2007/05/31/sharepoint-orphans-explained.aspx

Happy upgrading!