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

Revival checklist #515

Open
14 of 19 tasks
hmaarrfk opened this issue Oct 22, 2022 · 4 comments
Open
14 of 19 tasks

Revival checklist #515

hmaarrfk opened this issue Oct 22, 2022 · 4 comments

Comments

@hmaarrfk
Copy link
Collaborator

hmaarrfk commented Oct 22, 2022

  1. Avoid using is not when comparing to an integer #509
  2. Ensure the CIs are working again on with semi-modern versions of compilers + python
  3. Fix matlab compilation: Fix/matlab 2022 macos #513
  4. Update changelog with recent PRs - Update changelog for 1.11.2 #540
  5. Release new version
  6. Minor fixes for c++17/c++20 #511
  7. nose->pytest nose testing framework needs to be replaced #508
  8. deprecated functions deprecated implicit member functions #505
  9. Avoid use of deprecated libtiff types #510
  10. address Vigra pollutes builds with pragmas that suppress warnings #482
  11. Address simple warnings in the compilation
  12. Python 3.12 support? Rebuild for python312 conda-forge/vigra-feedstock#120 (comment)
  13. Release new version
  14. Rebuild vigra-numpy support Help needed to revive numpy support conda-forge/vigra-feedstock#134
    • numpy2 support
    • General new compiler support (Windows and OSX are breaking today).
@hmaarrfk
Copy link
Collaborator Author

I've pinned this issue for prominence.

Essentially, a lot can get unclogged if anybody is willing to help getting the OSX CI working again.

@hmaarrfk
Copy link
Collaborator Author

@k-dominik given that the CIs are back and running, I think we are good releasing a "quick version" without any other changes before moving on to changes to the code base.

This release mostly includes changes to the build architecture to bring it in-line with more modern tooling.

The follow-on PRs address compatibility with new standards of C++ when we can create a new version bump delineating the different changes for downstream.

@k-dominik
Copy link
Collaborator

Oh yes please, can't believe I finally can stop bumping build numbers manually for vigra when used as a dependency! Awesome that you put in the effort to make it work!

@hmaarrfk
Copy link
Collaborator Author

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

2 participants