How Drupal Contributors Track Changes Without Following Everything

Following Drupal development at scale requires more than reading issue queues, according to a blog post by Christian López Espínola. The author describes a workflow developed over more than a decade to stay informed without attempting to track every change directly. The approach begins with subscribing by email to all Drupal core issues, ensuring complete visibility rather than selective tracking.

The system relies on filtering and labelling incoming emails to organise issues by relevance and topic. Instead of reading each item in detail, the process focuses on scanning subject lines to identify patterns and areas of activity. When something stands out, it is followed more closely. This allows awareness to develop without the need to process every update individually.

The post identifies a gap between tracking issue activity and understanding what changes are actually committed. To address this, it references community efforts such as curated summaries of core commits and AI-assisted digests that condense large volumes of updates into readable formats. These summaries help bridge the difference between ongoing discussion and implemented changes.

The workflow is extended through a custom dashboard that aggregates feeds, including digest outputs, into a single interface. Combined with email tracking, this creates a layered system where updates are filtered, summarised, and reviewed in context. The post presents this as a practical method for maintaining awareness in a high-volume project without relying on a single tool or attempting full coverage.