#  ParaView 5.9.1-RC2 available for download 

**URL:** https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100
**Category:** Announcements
**Created:** [April 28, 2021, 6:55pm UTC](https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100 "2021-04-28T18:55:38Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![vbolea](https://discourse.paraview.org/user_avatar/discourse.paraview.org/vbolea/32/4121_2.png) [@vbolea](https://discourse.paraview.org/u/vbolea)
#### Post date: [April 28, 2021, 6:55pm UTC](https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100/1 "2021-04-28T18:55:39Z")

</div>

🎉🎉🎉

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/](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](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Documentation/release/ParaView-5.9.1.md).

Please let us know if you find any problems.

Thanks!

The ParaView team

🎉🎉🎉

---

<div class="post-metadata">

### Author: ![olesenm](https://discourse.paraview.org/user_avatar/discourse.paraview.org/olesenm/32/17416_2.png) [@olesenm](https://discourse.paraview.org/u/olesenm)
#### Post date: [May 13, 2021, 2:05pm UTC](https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100/2 "2021-05-13T14:05:08Z")

</div>

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

---

<div class="post-metadata">

### Author: ![vbolea](https://discourse.paraview.org/user_avatar/discourse.paraview.org/vbolea/32/4121_2.png) [@vbolea](https://discourse.paraview.org/u/vbolea)
#### Post date: [May 13, 2021, 3:45pm UTC](https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100/3 "2021-05-13T15:45:55Z")

</div>

It should be out by the end of this week 🙂

---

<div class="post-metadata">

### Author: ![olesenm](https://discourse.paraview.org/user_avatar/discourse.paraview.org/olesenm/32/17416_2.png) [@olesenm](https://discourse.paraview.org/u/olesenm)
#### Post date: [May 13, 2021, 3:49pm UTC](https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100/4 "2021-05-13T15:49:29Z")

</div>

good - sooner than expected

---

<div class="post-metadata">

### Author: ![todoooo](https://discourse.paraview.org/user_avatar/discourse.paraview.org/todoooo/32/2819_2.png) [@todoooo](https://discourse.paraview.org/u/todoooo)
#### Post date: [May 14, 2021, 2:05am UTC](https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100/5 "2021-05-14T02:05:39Z")

</div>

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

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [May 14, 2021, 2:40am UTC](https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100/6 "2021-05-14T02:40:34Z")

</div>

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](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4935)  
[!4927](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4927)  
[!4919](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4919)  
[!4910](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4910)  
[!4904](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4904)  
[!4897](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4897)  
[!4894](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4894)  
[!4892](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4892)  
[!4888](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4888)  
[!4884](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4884)  
[!4883](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4883)  
[!4882](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4882)  
[!4851](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4851)  
[!4743](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4743)  
[!4874](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4874)  
[!4858](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4858)  
[!4856](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4856)  
[!4853](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4853)  
[!4796](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4796)  
[!4789](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4789)  
[!4867](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4867)  
[!4595](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4595)  
[!4859](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4859)  
[!4792](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4792)  
[!4786](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4786)  
[!4784](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4784)  
[!4773](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4773)  
[!4733](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4733)  
[!4732](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4732)  
[!4734](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4734)  
[!4729](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4729)  
[!4692](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4692)  
[!4710](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4710)  
[!4706](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4706)  
[!4700](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4700)  
[!4688](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4688)

---

<div class="post-metadata">

### Author: ![todoooo](https://discourse.paraview.org/user_avatar/discourse.paraview.org/todoooo/32/2819_2.png) [@todoooo](https://discourse.paraview.org/u/todoooo)
#### Post date: [May 14, 2021, 3:27am UTC](https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100/7 "2021-05-14T03:27:04Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![todoooo](https://discourse.paraview.org/user_avatar/discourse.paraview.org/todoooo/32/2819_2.png) [@todoooo](https://discourse.paraview.org/u/todoooo)
#### Post date: [May 14, 2021, 4:16am UTC](https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100/8 "2021-05-14T04:16:56Z")

</div>

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

---

<div class="post-metadata">

### Author: ![olesenm](https://discourse.paraview.org/user_avatar/discourse.paraview.org/olesenm/32/17416_2.png) [@olesenm](https://discourse.paraview.org/u/olesenm)
#### Post date: [May 14, 2021, 7:37am UTC](https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100/9 "2021-05-14T07:37:22Z")

</div>

> [@cory.quammen](#):
>
> No, only select MRs go into the release branch, which is what 5.9.1 is based on.

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.

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [May 14, 2021, 5:49pm UTC](https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100/10 "2021-05-14T17:49:03Z")

</div>

> [@todoooo](#):
>
> So it looks like my changes for utf8 support have not made the cut.

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

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [May 14, 2021, 5:49pm UTC](https://discourse.paraview.org/t/paraview-5-9-1-rc2-available-for-download/7100/11 "2021-05-14T17:49:42Z")

</div>

> [@olesenm](#):
>
> What is your opinion, will we see a 5.9.2 or a 5.10.0 first?

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