maintenance

Nobody Home...

This is a tough time for blog reading junkies like me. I like to spend some of my time in the evenings winding down by reading CMS related blogs. Well, it seems some of my favorite blogs have decided to take a vacation. For example, many of the working group blogs found at Joomla.org are down.

No problem, right? I can can always visit some of the blogs I have listed in my blogroll. However, you'll also find Jeff Eaton's blog (Drupal) has been down for some time. Recently, JoeJoomla's blog has also been offline. Perhaps, it is time I find something else to do for relaxation...like talk to the wife. That's a new idea...and a good one too.

 

Drupal.org: Keeping Drupal 5.x up to date with Update Status module

Oh, yes!  I'm excited to try the new Update Status module for Drupal out.  The SMF Forum has had this notification feature for some time, though mostly for the "core".  It's a very nice feature to have for Drupal as it is getting very difficult to keep track of all the module updates.
Keep your Drupal 5.x site up to date with Update Status module -

Thanks to the hard work of several contributors, drupal.org can now automatically provide information about the latest official releases of drupal core and any contributed modules. The Update status module can check this information to tell you if your site needs to be updated. While it does not have information about development releases or modules acquired via CVS, if your site uses primarily officially released modules, you can easily tell which of your modules need to be updated.

This module will inform you that you are out of date by visiting the main administration page, and another page displays the status of Drupal and your installed modules. For more information, there is a Frequently Asked Questions available on the update status project page!

[Drupal.org]
Kudos to the contributors!

CIO Insight: How to Manage Application Enhancements

"One of the endless challenges for a large corporate software engineering organization is to develop an effective process for handling the steady stream of small changes, fixes and enhancements that seem to accumulate around installed software, both custom developed and Commercial of the Shelf (COTS)—no matter how good it is initially. Typically, these changes can be handled by a single engineer, don't require much resource or elapsed time and are generally pretty well defined. Users know that they are not asking for much, and don't, therefore, expect to have to wait very long to get their change request implemented."

Complete Story

Syndicate content