Skip to content

Commit 8a4d117

Browse files
committed
Add explanations for used abbreviations
1 parent 4f80ed7 commit 8a4d117

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

project/RELEASES.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,10 @@ flowchart TB
139139
reject(["The PR is not backported"])
140140
```
141141

142+
CVE stands for Common Vulnerabilities and Exposures and in the chart above it means an issue with an CVE-ID assigned to it.
143+
144+
CB stands for Community Build, and by full CB we mean the full run of [the Scala 3 Open Community Build](https://github.com/VirtusLab/community-build3).
145+
142146
## How should things be backported?
143147

144148
The backporting process is tracked by [a GitHub Project](https://github.com/orgs/lampepfl/projects/6) in the lampepfl organization. Every PR merged to the `main` branch is automatically added to the `Needs Assessment` column. Those PRs are reviewed by the release officer or other appointed person. They can decide to remove them from the project (backport rejected) or to move them to the `Backporting in progress` column. If the PR with the backport has any differences from the original PR, the person doing the backport will ask the author and reviewers of the original change to review the backport. After merging the backport, the PR will be moved to the `Backport done` column and, after the release, to the `Released` column.

0 commit comments

Comments
 (0)