This forum is for news and announcements to the Drupal community at large.

beta.drupal.org is ready to QA!

The drupal.org redesign team is looking for people to help perform Quality Assurance (QA) testing of beta.drupal.org. We have been working on redesigning Drupal.org and are nearing the first launch. Some details still need work, and we need your help to find and fix them.

Major revisions will likely not be included in this first launch; however, drupal.org is a community effort that is continually evolving. We want your feedback, and we want you to help continue to make our home better. There are opportunities for people of all skills to help us identify or fix problems.

Bill O'Connor (csevb10) and Neil Drumm (drumm) are leading the QA effort and can be reached in #drupal-redesign on IRC or in the redesign issue queue.

We need help with functional testing and cross-browser/platform theme testing. We will be periodically pushing changes, so the community will see progress on resolving issues.

Join the Views Bug Squad

As maintainer of an important project on drupal.org, one of the most challenging and time consuming parts of the job is managing the issue queues. When there are hundreds of thousands of users on a project, there is bound to be a lot of activity on that package, from asking for support, asking for new features, and finding bugs. The rate at which an issue queue grows is related both to the quantity of people entering issues into it, but also the quality of the maintenance of the queue. Sometimes, even simple maintenance on a queue is very time consuming and distracts from the other myriad responsibilities that a maintainer has.

In the Drupal Handbook, we have instructions on performing triage in various queues. Naturally, that article focuses on the Views queue, because it is one of the five most difficult queues to manage on drupal.org. The things it focuses on are relatively easy tasks, with some suggestions. Additionally, Views has a well defined issue submissions guideline that helps inform users how to submit issues, but also can help reviewers determine if an issue simply needs to be kicked back to the submitter for more information.

Drupal Fit: Drupal's fitness movement and support group

Dries Buytaert stands in front of a large, fiery explosion while flexing his muscles (original photo by Karlijn Buytaert and razzle-dazzled by Lee at Exaltation of Larks) The Drupal community has gotten large enough that community-focused groups are needed in order to help us take care of our own. LGBTQI Drupal, Drupalchix, Young Drupallers and Drupalgängers are all great examples. These aren't traditional working groups or regional user groups but they're essential for fostering the health of the community.

Drupal Fit is a movement to bring Drupal community members together and provide support for getting and staying fit. This movement started long ago at DrupalCons when community members met for early morning runs and group yoga, and the Drupal Fit group, on Drupal.org infrastructure at groups.drupal.org/fit, both acknowledges and promotes this movement.

Some of the goals of this group are:

Distributed Authentication (the drupal.module) on drupal.org will be turned off November 1st, 2010

Note: If you never used an "@drupal.org" login to a site then you can gleefully ignore this post. It was a feature launched long ago and not widely used.

Hey Everybody,

It's been a long time coming, but we are now approaching the point where the old "distributed authentication" mechanism will be turned off on drupal.org.

For a while, the distributed authentication method was a great idea. Sites like spreadfirefox.com used the distributed authentication and it helped spread awareness of Drupal. It was an early idea for identity and federated websites and distributed social and all those fancy buzzwords.

But while the concept might have been visionary the implementation was not. It is not a super secure architecture, as perhaps the biggest complaint.

So, we will turn it off on drupal.org on November 1st, 2010.

Scheduled Downtime

Drupal.org will have some scheduled downtime, Wednesday October 13th At 22:00 UTC (3PM PDT, 6PM EDT). We will be replacing our current NFS server with a HA-NFS cluster during this outage. We don't expect this outage to last more than an hour and thank you for your patience.

Drupal 7.0 beta 1 Released

Update: Drupal 7.0 Beta 2 is available now!

Our final Drupal 7 alpha version was released about three weeks ago. Today, we're proud to announce the first beta version of Drupal 7.x for your further testing and feedback!

The jump between alpha to beta means the following:

  • We think that we have resolved all critical data loss and security bugs in Drupal 7.
  • We think that our APIs are now frozen enough so that contributed module and theme authors can start (or pick up again) their #D7CX pledges.
  • We think that we have caught and fixed most of the problems with the upgrade path. We were able to successfully upgrade a copy of the Drupal.org database to Drupal 7.

That said, we definitely still have some bugs to shake out, and we need your help to find them! Especially new folks who haven't taken Drupal 7 for a spin yet. So please, do so, and let us know what bugs you find in the "Drupal core" issue queue (Please search incoming issues before filing).

What's new?

Tons of stuff! A revamped user interface, a new admin and default core theme, image handling in core, fields (CCK!) in core, module and theme upgrades from within the browser, an automated testing framework with over 24,000 tests, improved security and scalability, revamped database, AJAX, and file systems, jQuery 1.4, jQuery UI 1.8, RDFa, and literally gazillions of other things! Please see CHANGELOG.txt for a comprehensive list of all improvements in Drupal 7.

Pages

Subscribe with RSS Subscribe to RSS - News and announcements