Core change policies

This section contains policies about making changes in Drupal Core, including bug fixes and new features.

Allowed changes during Drupal core release cycles

This policy explains what changes can be made to different core versions during the Drupal core release cycle.

Backport policy

Assigning a version to an issue

Change records

Getting started with adding a change record for Drupal core.

Continuous upgrades between major versions

The guidelines used to create a continuous upgrade path from the previous major release.

Core gates

Core changes must pass through a series of "gates" to ensure their quality is up to standards.

Criteria for evaluating proposed changes

Criteria for reviewing and approving proposed changes to Drupal core

Drupal core backend backwards compatibility and internal API policy

What parts of the Drupal codebase are considered stable and reliable APIs, and which are not

Drupal core frontend backwards compatibility (BC) policy

This document defines the backwards compatibility policy for the Drupal frontend (render arrays, themes, markup, CSS, and JavaScript).

Experimental modules and themes

Modules and themes that are in development but not quite stable yet

How to deal with a random test failure

What to do if you encounter a random test failure

How to deprecate

A list of what can be deprecated and how to do implement the deprecation.

How to deprecate and remove an extension

Module or theme deprecation and removal process

Set platform requirements

Criteria for setting platform requirements such as PHP and Database versions.

Supported browser approval

Guidelines for selecting the browsers supported.

Guide maintainers

quietone's picture
xjm's picture