From 2d9784bce6f532b0f23b82e152a0444e33253a23 Mon Sep 17 00:00:00 2001 From: Ojus Chugh Date: Sun, 3 Aug 2025 06:55:21 +0530 Subject: [PATCH] =?UTF-8?q?docs:=20add=20=E2=80=98What=20is=20a=20backport?= =?UTF-8?q?=3F=E2=80=99=20definition=20to=20Backporting=20guide=20(fixes?= =?UTF-8?q?=20#620)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- src/release/backporting.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/release/backporting.md b/src/release/backporting.md index d71cb6ae4..804cde9bf 100644 --- a/src/release/backporting.md +++ b/src/release/backporting.md @@ -1,5 +1,12 @@ # Backporting +> ## What is a backport? + +> A **backport** is the act of taking a fix or feature that landed in a newer Rust release +> (or any software) and re-applying it to an older supported branch. This is most often used +> to ship critical bug-fixes or security patches on channels (like Stable or Beta) +> that no longer receive every upstream change. + There's a steady trickle of patches that need to be ported to the beta and stable branch. Only a few people are even aware of the process, but this is actually something anybody can do.