mirror
/
mongo
mirror of https://github.com/mongodb/mongo
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

SERVER-109254 Explain how last-lts and last-continuous are resolved (#40044) 

GitOrigin-RevId: 3a3e51bc64e13b5e49a0a5b8e75dbbdf35f6bd45
This commit is contained in:
Sean Lyons 2025-08-13 18:26:16 -04:00 committed by MongoDB Bot
parent 95c2b5c072
commit 823b6a3cb7
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/evergreen-testing/multiversion.md
View File

@ -34,10 +34,16 @@ For some of the versions we are using such generic names as `latest`, `last-lts`
- `latest` - the current version. In Evergreen, the version that was compiled in the current build.
- `last-lts` - the latest LTS (Long Term Support) Major release version. In Evergreen, the version
that was downloaded from the last LTS release branch project.
that was downloaded from the last LTS release branch project. It resolves to an entry
in `longTermSupportReleases` of [releases.yml](../../src/mongo/util/version/releases.yml).
- `last-continuous` - the latest Rapid release version. In Evergreen, the version that was
downloaded from the Rapid release branch project.
downloaded from the Rapid release branch project. It resolves to the entry in
`featureCompatibilityVersions` of [releases.yml](../../src/mongo/util/version/releases.yml)
that looks older than the output of `git describe`. Will not be tested against if it is listed in
`eolVersions` as being end of life.
Note: The latest release.yml file from master is always used, even fetched remotely when on another branch.
### Old vs new