Skip to content

Conversation

@Neves-P
Copy link
Member

@Neves-P Neves-P commented Oct 10, 2025

This is a draft PR to kick start work on EESSI versions.

It is currently a draft because a lot of information must still be added, and we may consider changing the structure or organization of some of the existing and new documentation pages to reflect the existence of different versions.

Feel free to push commits to this branch to expand the docs, or to modify what is already added.

Note: this PR also adds a link and fixes a formatting issue in the systems.md page

@@ -0,0 +1,20 @@
# EESSI Versions

EESSI is organized in different dated versions. Each EESSI version contains a version of the [compatibility layer](compatibility_layer.md) and its' own set of software applications. In addition, a particular EESSI version will target a different set of [common toolchains](https://docs.easybuild.io/common-toolchains/) to build software with. As an example, the first production EESSI version was released in June 2023 and is named `2023.06`. It contains the production release of the compatibility layer used to build software, and contains software build using the `foss/2022b`, `foss/2023a`, and `foss/2023b` [software toolchains](https://docs.easybuild.io/common-toolchains/#common_toolchains_overview) as defined in EasyBuild.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think people will understand what 'the production release' means. Isn't an EESSI version essentially related to a fixed version of Gentoo-prefix for the compat layer? I mean, we apply security updates, but we don't update the version of Gentoo-prefix itself, or do we?

If my understanding is correct, I'd state something like: "Its compatibility layer is based on Gentoo-Prefix version XYZ, and the software layer containers software build using the ... toolchains".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good point, I removed "production release" as a term, it's vague enough internally, let alone for users at large.

I tried addressing this in 1c67dba. From speaking with @bedroge , we don't pin the compat layer to a particular version (Gentoo Prefix doesn't have version), but we do so to a specific commit, with security patches added on top when needed. I'm not sure this is particularly relevant for most people, but at least the information is there.

Copy link
Collaborator

@casparvl casparvl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some minor points, see my suggestions.

@Neves-P Neves-P requested a review from casparvl October 28, 2025 13:42
@Neves-P Neves-P marked this pull request as ready for review October 28, 2025 13:50
@Neves-P
Copy link
Member Author

Neves-P commented Oct 28, 2025

Note, I've enabled the markdown footnotes extension with f0862b7.

Copy link
Collaborator

@casparvl casparvl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice, thanks Pedro!

Waiting for the CI check to complete... then it can be merged

@casparvl casparvl merged commit 3ed696f into EESSI:main Oct 29, 2025
1 check passed
@Neves-P Neves-P deleted the feature/2025.06 branch October 29, 2025 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants