doc/src/backport_policy: add maintainer changes to backport criteria (#2344)

Add maintainer changes to the backport criteria to remove ambiguity
about whether they are included in the existing CI condition.

Maintainer changes should be backported to keep maintainer notifications
in sync between the unstable and stable branches.

Link: https://github.com/nix-community/stylix/pull/2344

Reviewed-by: 0xda157 <da157@voidq.com>
This commit is contained in:
Noah Biewesch 2026-06-05 19:01:14 +02:00 committed by GitHub
parent 6b6b874d08
commit a168911ef0
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -6,7 +6,7 @@ applied to the current stable (`release-*.*`) branch.
To reduce maintenance efforts and improve stability on stable branches, security
fixes, bug fixes, and CI changes are backported, while new features, modules,
and theme improvements are not backported. Upstream changes causing theming
issues are considered a bug.
issues are considered a bug and maintainer changes are considered as CI changes.
New modules and theme improvements may be backported when explicitly requested
and backporting is trivial.