-
Notifications
You must be signed in to change notification settings - Fork 230
ReleaseProcess
Thomas Roehl edited this page Nov 20, 2020
·
4 revisions
LIKWID uses a three digit release version: ... For preparing a new major or minor release in advance a feature freeze in the main branch is enforced by tagging with:
v<major version>.<minor version>.<bug fix>-rcX
After it is decided that a version is ready for release the main branch is tagged with:
v<major version>.<minor version>.<bug fix>
and a branch is created. The release tar ball is then created from this branch. Bug fix are applied on the release branch and if applicable backported to the main branch. Bug fix release are generated from the release branch only. On a bug fix release the release branch is tagged with:
<major version>.<minor version>.<bug fix>
- Inform SPEC Tools team to update their LIKWID webpage by writing a mail to [email protected]
- Update LIKWID SPEC file in OpenHPC
- Update LIKWID recipe in the package manager spack
- Inform maintainers for various package managers (Debian, Archlinux, Gentoo, ...)
-
Applications
-
Config files
-
Daemons
-
Architectures
- Available counter options
- AMD
- Intel
- Intel Atom
- Intel Pentium M
- Intel Core2
- Intel Nehalem
- Intel NehalemEX
- Intel Westmere
- Intel WestmereEX
- Intel Xeon Phi (KNC)
- Intel Silvermont & Airmont
- Intel Goldmont
- Intel SandyBridge
- Intel SandyBridge EP/EN
- Intel IvyBridge
- Intel IvyBridge EP/EN/EX
- Intel Haswell
- Intel Haswell EP/EN/EX
- Intel Broadwell
- Intel Broadwell D
- Intel Broadwell EP
- Intel Skylake
- Intel Coffeelake
- Intel Kabylake
- Intel Xeon Phi (KNL)
- Intel Skylake X
- Intel Cascadelake SP/AP
- Intel Tigerlake
- Intel Icelake
- Intel Icelake X
- Intel SappireRapids
- Intel GraniteRapids
- Intel SierraForrest
- ARM
- POWER
-
Tutorials
-
Miscellaneous
-
Contributing