Starting with v9.4.0, VTK will follow a regular (calendar-based) release plan.
Expect a minor release every 6 months with intermediate patch releases in between, as needed.
Depending on the features added to the release, the release may become a major release.
The master and release branches will split one month before the scheduled release date. Please ensure that all feature branches are merged before the split.
A proposed detailed release plan will be announced a few weeks before each release.
Following this schedule, the next planned releases are as follows:
VTK v9.4.0 is planned for November 2024
VTK v9.5.0 is planned for May 2025
Specific planning for 9.4.0 release:
10/05/2024: Release split, no new features will be going into VTK 9.4.0 after this date
10/05/2024 to 11/05/2024: Release candidates are published and tested. Critical bug fixes are integrated into the VTK release branch.
In this release candidate we could not upload the VTK wheels to pypi due an issue that we are currently resolving it. We should have it fixed by the rc3.
and I will debug and release side-by-side where debug was post-fixed with “d”.
Now, no matter if my dependent projects are debug or release, they always end up using the last lib and dlls that were installed, when linking like this
Building now. Report in an hour. No, it also didn’t work for 9.3.1. I guess it must have been a while ago that the TARGET_RUNTIME_DLLS were set correctly for multi-configuration builds in the configuration files in the lib/cmake/vtk-XX folder.
In RC3, third party HDF5 is badly out of date at 1.13.1, almost two years old. This version is now marked experimental, and deprecated. Please update to the latest stable version, 1.14.5. I suspect that you will not run into any significant API problems, unless VTK is using certain HDF5 advanced features. See the latest HDF5 information: