One of the coolest features that made it into Drupal 7 without much (if any) fanfare is the Queue API. Drupal's Queue API is a pluggable system that allows you to queue events for later processing. Many systems, both in core (e.g., Batch API) and contrib (e.g., Feeds, Notifications, etc.), leverage the Queue API system.
If you have a content manager that likes to use inline images in the Body field of a Drupal site, you might run into an issue where they want an image inserted at the beginning of the field but don't want it to display in a teaser. Of course, you could tell them to use the "Summary" part of the body field to manually set the teaser, but some content managers tend to forget about that, and you're also dealing with an issue of entering data twice. No one wants to enter anything twice if they don't have to (even if it is merely copy and paste).
Drupal 8 is currently slated for sometime Winter 2013 (which, to me, likely means early Q1 2014). Once D8 is released, Drupal 6 will no longer be supported.
That means no bug fixes. No security updates. Nada. Your site will be running on unsupported code. You don't want that.
UPDATE: IT'S CURRENTLY UP IN THE AIR IF D6 WILL HAVE LTS OR NOT. See this issue.
This will get the webhook IP/CIDR from the Github API and output them as a comma separated list for easy import into firewall configs.