Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 2.5 #2469

Open
4 of 30 tasks
smehringer opened this issue Nov 1, 2021 · 1 comment
Open
4 of 30 tasks

Release 2.5 #2469

smehringer opened this issue Nov 1, 2021 · 1 comment
Assignees

Comments

@smehringer
Copy link
Member

smehringer commented Nov 1, 2021

Checklist

Preparation #2470

  • Freeze master/develop
  • Bump develop version to 2.5.0
  • Make sure that app versions are greater than the last packages on http://packages.seqan.de (set as SEQAN_APP_VERSION in each app's CMakeLists.txt)
  • Make sure the changelog is up-to-date

Build Packages / tarballs

  • Prepare library source tarballs
  • Prepare binary tarballs for each app -- Linux (The Team)
  • Prepare binary tarballs for each app -- macOS (The Team)
  • Prepare binary tarballs for each app -- FreeBSD (The Team)
  • Prepare binary tarballs for each app -- Win32/Win64 (The Team)

Tag the Release

  • Tag the release
  • Publish the release on GitHub

Update Resources

  • Upload tarballs to packages.seqan.de and update
  • Build dox for docs.seqan.de
  • Build manual for the seqan.readthedocs.org
  • Tag KNIME builds on Jenkins for permanent versioning (The Team)

Post-release Version Changes

  • Bump SEQAN_VERSION macros to reflect the next release (include/seqan/version.h)
  • Bump app versions so that they reflect the next release / being in development
  • Update seqan and app versions in the resource.txt file on the server in Tübingen
  • Unfreeze master/develop

Announcements

  • Write a release announcement for https://www.seqan.de
  • Send announcement to seqan-dev at lists.fu-berlin.de
  • Announce via seqan_lib Twitter account

Update upstream packages

  • macports
  • homebrew
  • debian
  • fedora
  • gentoo
  • ubuntu
  • openBSD
  • freeBSD
@eseiler eseiler pinned this issue Nov 1, 2021
@marehr
Copy link
Member

marehr commented Nov 11, 2021

What I noticed is that cmake 3.8 isn't working with seqan.

What I needed to change in stellar was the way to find python:

--------------------------- test/cli/CMakeLists.txt ---------------------------
index 26bb7f4d0..ae2145b41 100644
@@ -5,19 +5,19 @@ add_custom_target (cli_test ALL)
 # ----------------------------------------------------------------------------
 # Setup SeqAn 2 Tests
 # ----------------------------------------------------------------------------
 find_path (SEQAN_APP_TEST_PYTHON_LIB_DIR NAMES seqan/app_tests.py HINTS "${STELLAR_ROOT_DIR}/lib/seqan/util/py_lib/")
 macro (seqan_add_app_test APP_NAME)
-    find_package (Python3)
-    if (Python3_Interpreter_FOUND)
+    find_package (PythonInterp 3)
+    if (PYTHONINTERP_FOUND)
       add_test (NAME app_test_${APP_NAME}${ARGV1}
                 COMMAND ${CMAKE_COMMAND} -E env
                             PYTHONPATH=${SEQAN_APP_TEST_PYTHON_LIB_DIR} # make seqan/app_tests.py available
-                        ${Python3_EXECUTABLE}
+                        ${PYTHON_EXECUTABLE}
                         ${STELLAR_ROOT_DIR}/test/cli/run_tests${ARGV1}.py
                         ${STELLAR_ROOT_DIR} ${CMAKE_BINARY_DIR})
-    endif (Python3_Interpreter_FOUND)
+    endif (PYTHONINTERP_FOUND)
 endmacro (seqan_add_app_test APP_NAME)

https://cmake.org/cmake/help/latest/module/FindPython3.html is only available since cmake 3.12

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

No branches or pull requests

3 participants