Starting with ParaView 6.0, the ParaView development team will coordinate with the VTK development team on releases. That means a ParaView minor release will be compatible with a VTK minor release.
Accordingly, we will aim to closely follow the VTK 9.5 release schedule.
05/12/2025: VTK release split, no new features can go into VTK 9.5 after this date
05/14/2025: ParaView release split, no new features can go into into ParaView 6.0 after this date
05/14/2025 to 06/16/2025: Release candidates are published and tested. Critical bug fixes are integrated into ParaView and VTK release branches.
Update: we are working to resolve an issue with source/filter documentation generation; once that issue is resolved – and assuming there are no other showstoppers reported during the week after RC2 is released – ParaView 6 will be released.
That puts the ParaView 6 release no earlier than the first half of July.
Update: we have identified a couple issues in ParaView 6.0.0-RC2 and plan to release ParaView 6.0.0-RC3 about July 15 or 16. Assuming no additional critical problems are found in that version, we will use that as the 6.0.0 final release, and expect that to be out the week starting July 21.
Hello. Windows version of RC2 doesn’t store any settings. Every time I run it, I have default settings of all I changed before. Integration with MED reader has the same bugs a two versions before.
BTW I’m not using Salome Platform for post processing. There are other issues with the software. I was hoping you coudl do something about the reload function. It’s annoying when you have to recreate all the filters just to see the outcome again.
If you are talking about the small double blue arrow in the MEDReader, it is part of the MEDReaderPlugin which is developped by Salome and shipped with ParaView binary release for easier communication between pure ParaView and Salome.
