For background and to file new issues, please use the DrupalCI queue. We'll move it to other modules as necessary.
This is the module that takes patches posted in the Drupal.org issue queue and sends them off to dispatcher.drupalci for dispatch to aws testbots.
It provides Project module integration for DrupalCI. The integration serves to make automated testing and review part of the development workflow without requiring effort on behalf of the developer.
Information transfer
All requests are sent to the dispatcher using the Jenkins API. Cron is used to notifiy the dispatcher of a pending test request, which then may need a new aws instance to be provisioned and as such there is a short lag time between the event occurring and the time it has been completely processed.
Triggers
Projects can be configured per environment to test daily for a project, or ever time a commit happens, or each time a patch is submitted as well as per commit.
Block Page Visibility enables site developers to centralize the display of blocks to a single PHP function. It is an alternative to controlling display via each block's configure form.
Edit term provides links on taxonomy listing pages to directly edit taxonomy terms.
This makes it easier to immediately edit term name, synonyms, description, and weight for the term you are viewing without navigating through your site's administrative back end.
On the term edit page, you also have the new ability to set an URL-alias for the term directly, and create and position a menu item - the same way as can be done for nodes. See illustration.
Once changes are made, you are returned to the listing page from which you started, cutting normal term management procedure down from a dozen clicks to just two.
This module is discontinued at the moment.
I am not maintaining any Drupal 5 sites at the moment, so it is very unlikely to have any updates of this module. As to Drupal 6 there are better way of optimizing database problem. If someone wants to take over, please let me know.
Allows users (everyone, including admin) to cache queries for a certain time. It works perfectly with tables like 'system', 'variables', etc. These tables hardly ever change during the standard application life.
Used on high traffic pages (5 million pages per month, 40000 users). Works perfectly well.
This module is useful if you fight with overloaded database server.