webchick.net

very helpful lioness

drupal 7

Hit-list for top Drupal 7 module stabilization

Fri, 11/11/2011 - 00:27 -- webchick

Back in September, http://drupalcontribstatus.com/ was launched to track the porting status of the top 60 contributed projects to Drupal 7. Since then, we've whittled the list down to just 20 projects remaining, as well as tons of progress on the rest! YEAH!

I contacted each of the maintainer(s) of those remaining projects and have come up with a list of next steps for each. Your help is needed if we want to get that graph up to 100% by year's end. (Just in time for Drupal 7's first birthday! :))

As a general rule, help is needed in the following areas:

  • Issue queue triage (Difficulty: Novice): Going through the issue queues of these modules and doing things like closing duplicate reports, verifying that bug reports are valid, and so on. None of this is particularly difficult work, but time that maintainers have to spend doing it is time they can NOT spend porting their modules to Drupal 7.
  • Reviewing patches (Difficulty: Intermediate): Going through the issues in the queue marked "needs review" and making sure patches still apply, then testing to make sure that they still work, then reporting on the results of your testing are all critical things that really help save maintainers time, and ensure that any actionable issues are escalated to their attention.
  • Experience in various core sub-systems (Difficulty: Intermediate to Advanced): If you know how to write automated tests, are familiar with how the render API works, can answer questions about the new Field API or File API, there are several issues identified that could use YOUR help! Note that you don't necessarily need to be in MAINTAINERS.txt to provide this help, either; if you've already started building Drupal 7 sites and modules, you likely know enough to be helpful!
  • Co-maintainership (Difficulty: Intermediate) Many of these projects are seeking co-maintainers. If you or your business/customers depend on any of these modules, investing solid time in the issue queue to help review and roll patches for issues in need would be of tremendous benefit, and would help position yourself to ask for commit rights so that you can ensure these modules stay solid going forward.
  • JavaScript knowledge! (Difficulty: Intermediate to Advanced) Seriously. We are, generally speaking, a bunch of PHP nerds. If you know JavaScript, you can be helpful on a number of different (and important) fronts.

So, without further ado, here are some specifics on how you can help Drupal 7, and the maintainers whose code you rely on!

Drupal Core Diaries: 7.4 -> 7.7. OMG WTF BBQ?

Thu, 07/28/2011 - 19:13 -- webchick

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!

O'Reilly Webcast on Drupal 7 tomorrow!

Tue, 07/19/2011 - 11:55 -- webchick

The fabulous and ever-entertaining Jeff Eaton and myself will be presenting about Drupal 7 tomorrow on an O'Reilly Webcast about What' new and cool in Drupal 7? at 10am - San Francisco | 6pm - London | 1pm - New York | 10:30pm - Mumbai.

We'll cover some background on the Drupal project, what some of the biggest new cool features are in Drupal 7, impart tips on upgrading, and leave lots of time for Q&A. Please Register now if you'd like to join us! :D

The impact of the #D7CX movement and next steps

Mon, 07/18/2011 - 10:06 -- webchick

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.

A month (and a bit) in the Office of the CTO

Wed, 06/29/2011 - 00:05 -- webchick

Last month, I started my new job in Acquia's Office of the CTO. I posted my to-do list last month of a given week's worth of work, to try and provide some insight as to what I'm working on. Since that probably reads as chicken-scratch to you (my handwriting tends to be one-way encryption ;)), here are some of the highlights:

Proposal: Create a predictable schedule around Drupal 7 point releases

Mon, 05/23/2011 - 11:59 -- webchick

Due to a variety of factors, there hasn't been a point release of Drupal 7 since its 7.0 release, roughly 5 months ago. There are a lot of good bug fixes (some critical/major) and performance improvements in the 7.x branch right now, and the lack of these making it out there for public consumption yet has hampered the ability for contributed module authors to port their modules to Drupal 7, and several other bad effects.

Hey, MAINTAINERS.txt, we need your help!

Sun, 11/14/2010 - 01:22 -- webchick

For those who aren't aware, today here at BADCamp, Drupal 7 at long last reached 0 critical issues! YAY!!!

OMG ZERO!

We also released Drupal 7.0 beta 3. Why beta3 and not rc1? Please click the link for more details. :) (Spoiler: We wanted to leave room for one last hash through the "majors" queue and pre-string freeze clean-up)

So if you're a core subsystem maintainer, please try and find some time in the next day or so to triage your issue queue and make sure that we're not sitting on any release blockers we don't know about yet. Drupal 7 RC1 represents an "everything freeze", and is imminent.

All hands on deck for Drupal 7 alpha 1 this Friday!

Sun, 01/10/2010 - 01:28 -- webchick

Greetings, folks!

As you may or may not have heard, on Friday we are going to roll Drupal 7.0 Alpha 1. This will be the very first time that the vast majority of the community (not to mention the outside world) will download Drupal 7, and play around with all of the hard work you've all been doing for the past ~24 months. So! I would love to do everything that we can to really shine it up over the next couple of days.

Drupal 7.0 Alpha 1: Coming soon to a downloads page near you!

Wed, 12/30/2009 - 00:47 -- webchick

Drupal 7 first opened for development back in February 2008. At Drupalcon Boston a month later, we brainstormed on how to tackle some of Drupal's toughest challenges: our usability was not up to par, we were burning time fixing the same bugs over and over, our database abstraction layer suffered many limitations, upgrades were a nightmare, and critical modules such as CCK not being ported were harming our adoption rates of Drupal 6. Drupal 7 has made tremendous strides since then to solve each of these problems, as well as many others.

Pages

Subscribe to RSS - drupal 7