ParaView 5.9.1-RC2 available for download

Announcements
1

:tada::tada::tada:

The ParaView team is very happy to announce that ParaView 5.9.1-RC2 source code archives are available for download at

https://www.paraview.org/download/

Note: this release differs from v5.9.1-RC1 by a patch for MPI configuration on systems with SGI’s MPT. As such, we have not created precompiled binaries for this release candidate since they are essentially the same as those for v5.9.1-RC1. Only source tarballs are made available in this release candidate.

In addition, ParaView’s git repository and superbuild repository have been tagged with v5.9.1-RC2 and Spack package manager is being updated to include this new release.

All the documentation including tutorial, guides, references, and examples have been updated as well to reflect the all the new features included in this release.

Release notes are available here.

Please let us know if you find any problems.

Thanks!

The ParaView team

:tada::tada::tada:

2 Likes
2

Hi @vbolea - any guesses at the ETA for the 5.9.1 final?

3

It should be out by the end of this week :slight_smile:

1 Like
4

good - sooner than expected

5

How do we know which MRs have gone into this release? Everything up to 28 April?

6

No, only select MRs go into the release branch, which is what 5.9.1 is based on. The easiest way to see what went into 5.9.1 before it is tagged is to run

git log v5.9.0..origin/release

You can narrow it down to merge requests by grep’ing the output for “Merge-request”. I’ve turned these into links

!4935
!4927
!4919
!4910
!4904
!4897
!4894
!4892
!4888
!4884
!4883
!4882
!4851
!4743
!4874
!4858
!4856
!4853
!4796
!4789
!4867
!4595
!4859
!4792
!4786
!4784
!4773
!4733
!4732
!4734
!4729
!4692
!4710
!4706
!4700
!4688

7

I don’t have a v5.9.0 branch in my forked repository. Do I just need to add it as an upstream remote?

Edit: Nevermind. I just did a command-line fetch on the upstream Paraview repo and then used git-bash
git log v5.9.0..upstream/release | grep Merge-request

Thanks.

8

So it looks like my changes for utf8 support have not made the cut.

9

What is your opinion, will we see a 5.9.2 or a 5.10.0 first? There are various fixes for the OpenFOAM reader that I would like to get into the next release. If that is 5.10.0, I probably don’t have to do anything. If it is 5.9.2, probably need to start making some of these as backports from the vtk master.

10

For a patch version, we try to avoid including sweeping changes to many parts of the code. They’ll be in 5.10, though.

11

Unless there is something devastatingly wrong with 5.9.1, 5.10 will be the next release, scheduled for late 2021.

1 Like