Comment 1 for bug 1752025

Generally speaking, it's always the Evergreen community's recommendation to upgrade to newer and supported versions of Evergreen and not to re-use older versions of the code for too long to avoid complications or issues that have been solved on newer versions. This is especially important when dealing with potential security fixes or other concerns that are resolved in current versions but may not have been backported to older, legacy versions of Evergreen.

Past versions of Evergreen code are generally made available later as links on the Code Museum page, see: https://evergreen-ils.org/egdownloads/code-museum/

The links themselves are pointing at the downloads directory where the files are located, and does not usually change places. Past bug reports, blog posts, etc. will usually continue to work and point at the code.