From 5c7301af2f9e788ce870bd14294d7c2acd32e9c1 Mon Sep 17 00:00:00 2001 From: Jens Reidel Date: Mon, 10 Nov 2025 22:59:42 +0100 Subject: [PATCH] docs: Clarify process for demoting devices Signed-off-by: Jens Reidel Part-of: --- docs/device-categorization.md | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/docs/device-categorization.md b/docs/device-categorization.md index 74af7a8b4..8b80ae48c 100644 --- a/docs/device-categorization.md +++ b/docs/device-categorization.md @@ -181,8 +181,20 @@ straight to main. ### Moving to a lower category -If rules to keep a device in a category are no longer fulfilled, we should -create a merge request to move them to the now appropriate category. +If rules to keep a device in a category are no longer fulfilled, an attempt to +contact the device maintainers and make them aware of the situation must be +made. The maintainers then have two weeks to ensure the device meets the criteria +again. Maintainers can request additional time in response, but only up to one +more month from the time they were contacted. If a stable release is scheduled +for branching in that timeframe, additional time can only be requested up until +the date of the branching. + +If the maintainers cannot be contacted, or if two weeks and any additionally +requested time pass and the device still does not meet the criteria, a merge +request to move them to the now appropriate category should be opened. + +Merge requests moving a device to a lower category are subject to the standard +[pmaports approval rules](./approval-rules). ## See also