webchick.net

Some folks noticed that as of Wednesday's release, we went from 7.4 -> 7.7 and are a bit confused about what's going on, as well as why these releases happened in such rapid succession, so soon after the 7.4 release. Here's the skinny:

• As of Drupal 7.1/Drupal 6.21, Drupal core does monthly releases. This was a new policy the core team discussed and implemented back in May, which lays out a schedule of the last Wednesday of the month for new core releases.

  This policy change has helped tremendously to provide predicability for Drupal site maintainers so they don't need to fret every Wednesday about "what if" a new core release comes out, it's helped to ensure timely fixing of security issues, and also has encouraged a general "swarming" around bug fixes in a timely manner to ensure they make the next release deadline.

  The monthly rate will likely slow down as D7 continues to mature, but for now it's really helping to provide focus on working through some of the backlog and getting contributed module blockers unstuck.

• When security releases are required, we create two releases. One which has only the security patches, and one that has the security patches, plus all the bug fixes to date.

  Why do such a silly thing, you might ask? Because it's *really* important that security fixes get rolled out pronto, whereas the bug fix releases might conceivably need more testing to make sure they don't create any adverse effects in your environment. So we offer Drupal 7.5 for those who want only the quick fix, and Drupal 7.6 for the whole shebang.

  This graphic by Gábor Hojtsy, included on all release announcements, lays it out rather simply in flowchart form.

• Drupal 7.6 was accidentally rolled incorrectly, hence 7.7. The only difference between 7.7 and 7.6 is literally a one line fix to the VERSION number in bootstrap.inc (ok, fine, technically 3 lines because of CHANGELOG.txt ;P). I blame being holed up sick in a hotel room with a stomach flu for missing the git commit between vi bootstrap.inc and git tag. Sorry about that. :(

  Thankfully, some helpful friends are helping to work on some automation tools for the process so that doesn't happen again. :)

Hope that helps clarify things!

Back around the time of the Drupal 7 code freeze, Moshe Weitzman proposed the #D7CX (Drupal 7 Contrib Experience) movement. Developers were encouraged to add a #D7CX pledge to their project pages, indicating that they would port their contributed modules and themes to Drupal 7 by the time Drupal 7 was released.

Here is some data to measure the impact that this movement had, relative to Drupal 6, as well as some recommended next steps to help us complete the work that #D7CX started.

Pursuant to the new predicatably scheduled point releases of core policy, just a heads-up that there will be a new point release of Drupal 7 this Wednesday, June 29.

Here's a report from the first week at my new job!

TL;DR: In summary: intense, amazing week. My main focus for the next few weeks will be on core, particularly Drupal 7, and making it awesome. Can't wait to start.

:)

http://groups.drupal.org/node/114264 contains very important information that affects everyone who currently contributes or plans to contribute code to Drupal.org post-Git migration.

The Git migration team is urgently looking for feedback on this proposal from as many contributors as possible, so please ponder it over the holidays and chime in with your thoughts.

(Comments disabled here, because you should be commenting over there :))