Core development policies and practices

Drupal Core strategy

Drupal core expectations, goals and objectives

Core change policies

Policies about making changes in Drupal Core, including bug fixes and new features

• Allowed changes during Drupal core release cycles
• Backport policy
• Change records
• Continuous upgrades between major versions
• Core gates
• Criteria for evaluating proposed changes
• Drupal core backend backwards compatibility and internal API policy
• Drupal core frontend backwards compatibility (BC) policy
• Experimental modules and themes
• Frontend Developer tools for Drupal core
• How to deal with a random test failure
• How to deprecate
• How to deprecate and remove an extension
• Set platform requirements
• Supported browser approval

Core committer handbook

Guidelines, best practices, instructions, and references for Drupal core committers

• Reviewing and committing RTBC issues
• Reviewing a Drupal core private security issue
• Adding a new Drupal core committer
• Core committer orientation
• Configuring commit signing
• Email template for alerting all project maintainers of upcoming beta
• How credit is granted for Drupal core issues
• Add or remove a Subsystem or Topic maintainer
• Release management
• Facilitator Tasks
• [Archive] Adding and removing a Subsystem or Topic maintainer

Core dependency policies and practices

Policies about adding dependencies to Drupal Core

• Core dependency evaluation criteria
• Core dependency release cycles
• Current JavaScript dependencies
• Current PHP dependencies
• Managing composer updates for Drupal core

Core release cycles

Major, minor, and patch release schedules, and development roadmaps

• Drupal core release schedule
• Release process overview
• Prior to Drupal Core 8.0.0

Roles and responsibilities

This document outlines specifics particular to the provisional committer role.

• Differences between full and provisional core committers
• Past core maintainers