The open source Content Management System (CMS) Drupal has modified its guidelines on fixing security vulnerabilities. The project will now only work on vulnerabilities in the completed code of its modules. Modules that are in release- candidate mode will no longer be supported.
Drupal plans to work with module maintainers whose modules are code complete. The maintainers will also be a given a deadline within which the problem should be resolved. If the deadline is missed, the project and the module will remain unpublished. Vulnerabilities in unfinished code will be flagged in the module’s issue queue.
To read the full story, click here.
Sitecore Certification for Second Batch of WS Digital ExpertsMay 12th, 2010
WS CMS Partners are All Leaders in Gartner's Magic Quadrant 2015May 12th, 2010
Open Source vs Proprietary Platforms: What Works for Government2Citizen (G2C) PortalsMay 12th, 2010
Ektron + EPiServer - What Does the Merger Mean for Customers?May 12th, 2010
3 Reasons Why You Should Consider Upgrading to Ektron 9 Right Now!May 12th, 2010
Ektron 8.7 Brings Support For Cloud Computing, SharePoint And An Improved Editor To Make Your Life EasierMay 12th, 2010