Skip to content

Commit 6d0072b

Browse files
committed
Explain usage of backport lables
1 parent 09eea23 commit 6d0072b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

project/RELEASES.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ The backporting process is tracked by a GitHub Project in the lampepfl organizat
145145

146146
Maintainers can request backporting the entirety or a part of previously rejected PR by adding it to the `Backport requested` column.
147147

148-
Labels form the `backport:*` family retains their current meaning, i.e., they are used to mark things on the `main` branch that should be backported to the RC. Due to dropping the RCs for the Scala Next patch releases (more about it below), they will be only relevant for the Scala Next minor versions.
148+
Labels from the `backport:*` are used only for backports that targets versions with already released RCs. They can be used to mark changes on the main that are fixing a critical bug present in the Scala Next RC release or changes that were backported to the future Scala LTS versions that should be also backported to the current RCs.
149149

150150
## The release cycles
151151

0 commit comments

Comments
 (0)