Add clarification about backport labels

remove blank lines

Author: Kordyjan

project/RELEASES.md

@@ -137,12 +137,6 @@ flowchart TB
 
     acc(["The PR is backported"])
     reject(["The PR is not backported"])
-
-
-
-
-
-
 ```
 
 ## How should things be backported?
@@ -151,6 +145,8 @@ The backporting process is tracked by a GitHub Project in the lampepfl organizat
 
 Maintainers can request backporting the entirety or a part of previously rejected PR by adding it to the `Backport requested` column.
 
+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.
+
 ## The release cycle
 
 Releasing two different lines of the language at the same time requires some changes to the release procedures. We no longer release RC versions for patch releases of Scala Next. RC versions of patch releases of Scala LTS are released two weeks before the intended full release date. RC versions of Scala Next minor releases are released four weeks before the intended full release date.