A happy 2014! What a great year for a Drupal major release!
Have you started learning the new Drupal 8 APIs? Are you porting your modules forward to an 8.x branch? Are you a curious site builder ready to adopt the new hotness that will be Drupal 8?
Well now is the time to jump in and start learning. And one of the best ways to learn is to teach. Speaking from experience, authoring a change record is an excellent way to explore a sub-system of Drupal 8. You are, in a sense, documenting your personal learning as you work to understand the change, why the change was necessary and how users will write code against the new system. And everyone benefits from your efforts.
What is a change record? Well, when a significant change is made to Drupal, the developers and committers will require that a change record node be published that describes the updated code and if applicable, how the change alters a previously existing API. We have a detailed explanation of how to write a change record. Generally, you will spend 20 to 40 minutes on this task. Here is the current list of issues that require a change record. Right now there are about 40 issues that require a change record to be written.
Very often the developers involved with an issue patch will author the change record. When this does not happen, the issue is marked with a
Needs change record tag. Any open change records will block the creation of a Drupal beta or release candidate, so they must all eventually get written. Change records are a vital means to help Drupal developers understand how to alter their coding practice from Drupal 7 to 8.
If we got 40 people to each pick an issue and write up a change record, we could clear out the queue today! That's quite an achievable goal.