Skip to content

Added description for backport #925

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
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Added description for backport #925

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2d9784b
docs: add ‘What is a backport?’ definition to Backporting guide (fixe…
ojuschugh1 Aug 3, 2025
4870a9e
Merge branch 'master' into define-backport-620
ojuschugh1 Aug 2, 2025
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
7 changes: 7 additions & 0 deletions src/release/backporting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.

Expand Down