Acquia Drupal Launches, Drupal 7.0 Unstable releases begin

It was a big week for the Drupal project last week.

First, Acquia Drupal came out of beta and publicly launched. Second, Angela Byron announced the first release of Drupal 7.0-unstable.

Acquia Drupal 1.0 should be very good news for people who like Drupal but wanted a commercial supported version. It is based on the Drupal 6.4 release, including both core and selected community modules, including CCK and Views, but no WYSIWYG editor (full list here). Additionally, there are two “Acquia Network” modules, which serve to connect your Acquia Drupal install to the Acquia Network for support, update notifications, remote cron, anti-spam (using Mollom), and statistics.

(Full disclosure: Optaros has been participating in the beta program and expects to participate significantly in the Acquia partner program).

For more info, see Dries’s blog post, Jeff Whatcott’s launch round-up, read the official press release, or go download a copy and sign up for a (free as in beer until December 31, 2008) community subscription to the Acquia Network.

On the Drupal development list, Angela Byron announced the first of what will be many releases of Drupal 7.0, marked as “unstable.” Full detail on what’s included can be found in the changelog in CVS, but here are some of the highlights:

  • SimpleTest module in core with “a bazillion” tests (docs)
  • The new database API, also known as “Database: The Next Generation” (docs)
  • A code registry, which keeps in the database functions in modules, based on contents of .info files (docs)
  • new #input_format property on textareas
  • Image toolkits can now be supplied by modules
  • Two install profiles in core
  • More drag-and-drop in the admin areas
  • Descriptions on permissions, and node permissions sorted by content type

Remember this is clearly a developer install, marked “unstable” on purpose - don’t think you’re going to run this in production any time soon, but advanced testing of modules should help everyone avoid the “slow module porting” problem the community has experienced with Drupal 6.

Leave a Reply