Could we have a new VTK 9.x release soon?

Hi all,

While tracking down something recently, I noticed the current VTK release (9.0.1) doesn’t actually compile out-of-the-box on recent macOS / Xcode because of:

/VTK-9.0.1/ThirdParty/hdf5/vtkhdf5/src/H5Fsuper.c:1397:16: error: implicit declaration of function ‘vtkhdf5_H5O__fsinfo_set_version’ is invalid in C99
[-Werror,-Wimplicit-function-declaration]
if(H5O__fsinfo_set_version(f, &fsinfo) < 0)
^

This is fixed in the release branch already.

We recently merged another HDF5 change in the release branch that allows VTK to be built as a Universal Binary on macOS.

Between those two issues, it would be great to have a new release. It never looks good to new users when something doesn’t compile out-of-the-box. :slight_smile:

Cheers,

Sean

Yes can I add my voice to this as well, I’m looking to upgrade from an old QT and ancient VTK to QT5 and VTK… something? What version? I don’t know!

I checked the git repo, and there isn’t even any branches for version 8 hotfixes?
It seems like VTK has leaped into a continuous release model?

I haven’t found any documentation or real discussion around when 9.0.2 or 9.1.x is planned for release.
I did see some discourse from last year about 9.1 rc, with the deadline in October 2020,
what happened there? I haven’t found any follow-up discussion.

There seems to be a lot of API changes in the pipeline, how are others keeping their codebase stable? There are so many merge requests, must be a lot of thrash on the master?

And what is the “release” branch for exactly? Is this a “more stable” version of master?

I’m wondering if I should just be branching of version 8.20 …

Thanks,
Paul

I should also mention that this would be a good page to document the release plans:
https://vtk.org/Wiki/VTK/Roadmap

hasn’t been updated for 9.x at all yet …
If this approach has been abandoned, then some notes/suggestions/tips for new developers would be really helpful in that page…

Point made: It may be time for a hackathon so we can figure out how to better plan for and communicate about the roadmap etc.

There seems to be a lot of API changes in the pipeline, how are others keeping their codebase stable? There are so many merge requests, must be a lot of thrash on the master?

The point of running thousands of tests on multiple platforms on a continuous basis has the effect of keeping the software relatively stable. While the process is far from perfect, the fact that the current level of development is going on continues to astonishes me, especially considering that Ken and I cut the first lines of VTK code in December 1993 - coming up on 30 years now…

What version? I don’t know!

Use the last released version, 9.0.1

There is no hotfixes for previous version of VTK.

There seems to be a lot of API changes in the pipeline, how are others keeping their codebase stable?

Every single API changes implies a legacy code to ensure retrocompatibility. This is part of the VTK code guidelines.

There are so many merge requests, must be a lot of thrash on the master?

Each merged Merge Request is reviewed and merged by experienced members of the VTK community.

And what is the “release” branch for exactly? Is this a “more stable” version of master?

The release branch is used for new patch release (eg: 9.0.2 if it ever comes) and only contains bugfixes, it does not contains new features as master does.

I’m wondering if I should just be branching of version 8.20

You definitely should not. the VTK 9 breaking changes are for the better.

I should also mention that this would be a good page to document the release plans: hasn’t been updated for 9.x at all yet …

Indeed, the wiki is being phased out. You can find documentation about the VTK 9 changes and release notes here: VTK 9.0.0 - #6 by ben.boeckel

That being said, we definitely needs to improve and clarify this process.

Are you a VTK contributor @Paul_Harris ? Maintaining and improving a opensource project as complex a VTK is a very big task and we will take any help we can get.

Yes it’s an amazing project, and great to see there are still major changes from time to time - keeping it fresh.

I think I started working with VTK in 2008, mostly as a vis library.

Hum how did you reply inline Mathieu?
via email, I guess? Discourse doesn’t seem to have an inline reply button?



What version? I don’t know!

Use the last released version, 9.0.1

That is pretty old, and I want to avoid hitting old bugs that have since been fixed over the last 8+ months…

I saw a few bug reports that are in the release/master that could affect me - hard to tell.
Plus I may have a few patches to push up.

And what is the “release” branch for exactly? Is this a “more stable” version of master?

The release branch is used for new patch release (eg: 9.0.2 if it ever comes) and only contains bugfixes, it does not contains new features as master does.

I should also mention that this would be a good page to document the release plans: hasn’t been updated for 9.x at all yet …

Indeed, the wiki is being phased out. You can find documentation about the VTK 9 changes and release notes here: https://discourse.vtk.org/t/vtk-9-0-0/3205/6

Thanks, I’ll track that thread.

That being said, we definitely needs to improve and clarify this process.

Even just cleaning up old links on the wiki might help in the meantime.
For example, I noticed there was a link to the old bug tracker that doesn’t work.

Are you a VTK contributor @Paul_Harris ? Maintaining and improving a opensource project as complex a VTK is a very big task and we will take any help we can get.

I have contributed over the last (nearly) 2 decades, with a few small patches and bugfixes,
but they have mostly been lost in the bug tracker and not folded in due to lack of attention.

I don’t have time to do any extra contributions or work for the VTK cause specifically, but if I do need to patch VTK, I will be pushing patches / pull requests as best I can.

Just select the text and then click Reply.

That is pretty old, and I want to avoid hitting old bugs that have since been fixed over the last 8+ months…

I saw a few bug reports that are in the release/master that could affect me - hard to tell.
Plus I may have a few patches to push up.

Then use master