Skip to content

[docs] Document the backport of Site registration data #1505

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
andrewnicols wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[docs] Document the backport of Site registration data #1505

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions general/development/policies/backporting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,15 @@ As part of Moodle's commitment to accessibility, bug fixes for accessibility iss
- When the next LTS version is released, backporting of accessibility bug fixes will cease for the older LTS branch.
- For example, accessibility bug fixes will be backported to the Moodle 4.1 LTS branch from its release up to Moodle 4.4's release. However, when Moodle 4.5 LTS is released, accessibility fixes will no longer be backported to the 4.1 LTS branch.

### Other cases which will be backported whenever possible:

A small set of changes will automatically be considered for backport, including to security-supported releases. These include:

- changes to testing systems including both Behat and PHPUnit. This is to allow community developers to make use of features such as test helpers, transformations, generators, and-so-on for all supported versions of Moodle; and
- additional data collected for the purposes of Site Registration. This is to ensure that Moodle has an accurate overview of the technologies powering sites that Moodle runs on in order to make technical decisions about support and direction.

Care should be taken when backporting these changes, and only the minimum of change should be accepted. The introduction of new User Interfaces, for example, not supported by these cases.
Copy link

Copilot AI Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sentence is grammatically incorrect. It appears to be missing a verb (such as "is" or "are") between "for example," and "not supported". The sentence should read: "The introduction of new User Interfaces, for example, is not supported by these cases."

Suggested change
Care should be taken when backporting these changes, and only the minimum of change should be accepted. The introduction of new User Interfaces, for example, not supported by these cases.
Care should be taken when backporting these changes, and only the minimum of change should be accepted. The introduction of new User Interfaces, for example, is not supported by these cases.

Copilot uses AI. Check for mistakes.

## Process for requesting a non bug-fix backport

Improvements or new features can be requested to be backported to the stable branches. We urge developers to consider this request carefully. In recent years, Moodle has moved to a short and predictable time based release schedule and we use a very effective distributed source control system. Both of these process changes should ensure that a change not being backported to the stable branches is not as problematic as it may have used to be.
Expand Down