Skip to content

Commit 94c93c2

Browse files
ojuschugh1apiraino
andauthored
docs: add ‘What is a backport?’ definition to Backporting guide (fixes #620) (#925)
Co-authored-by: apiraino <[email protected]>
1 parent 9ad149d commit 94c93c2

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

src/release/backporting.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,13 @@
11
# Backporting
22

3-
There's a steady trickle of patches that need to be ported to the beta and stable branch.
3+
> ## What is a backport?
4+
5+
> A **backport** is the act of taking a fix or feature that landed in a newer Rust release
6+
> (or any software) and re-applying it to an older supported branch. This is most often used
7+
> to ship critical bug-fixes or security patches on channels (like Stable or Beta)
8+
> that no longer receive every upstream change.
9+
10+
There's a steady trickle of patches (mostly fixes of severe enough bugs) that need to be ported to the beta and stable branch after they're merged into the master branch.
411
Only a few people are even aware of the process, but this is actually something anybody can do.
512

613
## Beta backporting in `rust-lang/rust`

0 commit comments

Comments
 (0)