VTK 9.5.1 Release

Announcements
1

:tada: :tada: :tada:

VTK 9.5.1 has been released

This release includes several fixes for VTK. Find the changes in our release notes: https://gitlab.kitware.com/vtk/vtk/-/blob/master/Documentation/release/9.5.md

Downloads: https://vtk.org/download/
Python wheels are available on PyPI ( vtk · PyPI ).
We are also currently updating the VTK package in both conda-forge and Spack.

Thanks to all contributors

:tada: :tada: :tada:

3 Likes
2

Oh nice, great work!

(Is a maven update for the java wrapper scheduled by the way? For now I am using the version I compiled anyway, but I am considering switching to the maven version if it’s available)

3

Are there specific release notes for 9.5.1? The link just points to the 9.5 release, and from what I can doesn’t specify changes related to 9.5.1. Thanks.

4

Hello, apparently https://gitlab.kitware.com/vtk/vtk/-/blob/master/Documentation/release/9.5.md is 3 days old so I suspect it’s up to date?

5

We have merged the new release notes produced after 9.5.0 into the 9.5.md file.

6

Yeah, it’s pretty obvious that 9.5.md should have a separate section for 9.5.1 so that people can easily see what’s been patched since 9.5.0. @ben.boeckel can this be put into the release instructions so that it’s done for the 9.6 release series?

1 Like
7

https://gitlab.kitware.com/vtk/vtk/-/commit/783703c9f22a77cb50163cf590290ae7f681024f

1 Like
8

Indeed I was about to have a look at the diff as it’s all versioned anyway :smiley:

9

A diff isn’t a substitute for properly versioned release notes…

2 Likes
10

I can also see that it will be more desirable to add a section of the changes unique to each patch release, it does not have to even be the full release note but a intra-document reference to the it.

11

I just shared the info I had on hand. I agree with you @dgobbi :slight_smile:

1 Like
12

It isn’t, but it still helps ^^

As for the maven update, does anybody know if it’s still planned?

13

I believe the way CMake handles this is:

  • there is only a release file for X.Y
  • patch changes are merged into this single file
  • the patch release announcement contains just the patch’s changes

I believe the rationale is that anyone updating to X.Y should always use the latest patch version. Updating from 9.3 to 9.5.0 makes no sense now that 9.5.1 is out. So in that sense, it should always be a one-stop-shop for “what is new in 9.5.x”. However, for those doing the patch update, this thread is probably has far more awareness and we can provide such a summary here.

So instead of splitting the X.Y.md file and making prior minor version users have to read multiple documents, would it be sufficient to direct a (reformatting of) the release note file’s diff to be in this announcement thread’s opening post?

14

No-one suggested that. The proposals are:

  1. have a separate section in X.Y.md for X.Y.Z’s changes, or
  2. indicate via footnotes/references/etc which changes were made in X.Y.Z

Since the X.Y.Z notes are already being merged into X.Y.md, it should be trivial to do either (1) or (2) at the same time.

1 Like
15

Footnotes sound best to me; duplicating the overall structure feels quite excessive (whether in separate documents or a single one).

1 Like