releases

Events happening in the community are now at Drupal community events on www.drupal.org.
gengel's picture

Salsa Supporters BETA

Hey everyone,

There hasn't been much activity posted here in some time, so maybe this will get things rolling again. Has anyone done any interesting Salsa implementations recently? We have!

Read more
tylor's picture

Roadmap for 1.0 SMS Framework release

There has been some steady work to improve the SMS Framework module and I think it would be valuable to outline some thoughts on a 1.0 release. As far as new features the biggest ones will be the ability to receive messages and support for the Muse gateway. There will also be major improvements to user interface and scalability for the SMS User module.

Issues I would like to see resolved for a 1.0 release:
http://drupal.org/node/255095 - many improvements to SMS User
http://drupal.org/node/258057 - text messages should include more descriptive message

Read more
dww's picture

New system for releasing Drupal contributions

Cross-posting from http://drupal.org/node/77562 ...

We've seen explosive growth in 2005 and 2006 based the ability for Drupal sites to rapidly deploy new features that meet real world customer needs, not just fulfill technical requirements. This project aims to increase consultant and site administrators ability to effectively manage releases, security, versioning, issue tracking, and feature deployment into customer ready production environments. By directly improving the Drupal.org release and project management infrastructure we will speed up the life cycle for meeting customer and user requirements and ultimately improve the ability to manage Drupal web sites. Donating to this effort (via the PayPal link on the full proposal) provides funding to accelerate volunteer contributions the Drupal.org project maintainers have made over the past 8 months.

Overview

  • Contributions will have real releases and version strings, just like Drupal core itself
  • Security announcements will refer to exact versions of modules that are effected
  • Issues will be tracked by the exact version number of the contribution where the bug is present
  • Development branches for any given version of the Drupal core -- maintainers can add new features to their module or theme without endangering the stability of other code that is compatible with the same version of Drupal core.
  • All contributions will be clearly identified with the version of Drupal core they are compatible with

For the rest of the proposal, please see the full post on drupal.org.

Read more
Subscribe with RSS Syndicate content