Samuel Wein

Switching to CIBuildTools looks more complicated than expected. We already roll the wheel building process into our ctest call, but as far as I can tell there is no way...

This has taken the back seat to the FullMultiJob. I hope to get to it after finishing the other.

Still having issues with creating the tags, but other than that and updating the website everything is working.

Additional dependencies on our existing Jenkins infrastructure showed up when we turned off the UT stuff over the break. I've been working on them.

I added the creation of a src tarball as an artifact. Tagging (aside from the genericworkflownodes owned repo) works. The release text was getting mangled I've just committed a fix...

oh, and the naming right now is a hack, there weren't any release notes associated with 2.9.1 so I'm just using the name and notes from 3.0.0 (see https://github.com/OpenMS/OpenMS/blob/da1f58334530977a03ac5028602b5b1d6e79c3fb/.github/workflows/openms_ci_matrix_full.yml#L171)

> TUTORIALS Those have gotten moved out to a separate repo, so it's now not part of the release process.

> are you sure? @poshul can you link to that? I thought they might be part of the doxygen documentation? I think he is talking about the compiled C++ tutorials...

> In the "prepare the release candidate section" ; am I updating the version numbers to "3.2.0" or with a release candidate suffix like "3.2.0-rc1" or similar? I think you...

I don't *think* so. The minimum x86-64 microarchitecture level that supports avx also supports avx2 (x86-64-v3). On Thursday, October 10, 2024, Timo Sachsenberg ***@***.***> wrote: > do we also need...