GitLab

Preparatory steps

• Announce to paraview-developers@paraview.org

• Update ParaView guides

  • User manual
    • Uploaded
  • Catalyst guide
    • Uploaded
  • Getting Started
    • Uploaded

• Update release branch

  • Update version.txt

git fetch origin
git checkout -b update-to-5.5.0-RC2 origin/release
echo 5.5.0-RC2 > version.txt
git add version.txt
git commit -m 'Update version number to 5.5.0-RC2'
git tag -a -m 'ParaView 5.5.0-RC2' v5.5.0-RC2 HEAD

• Push new ParaView tag
  • git push origin update-to-5.5.0-RC2:release v5.5.0-RC2
  • Create GitLab merge request and merge it.

Create binaries

• Create source tarballs
  • ParaView (Utilities/Maintenance/create_tarballs.bash --tgz --zip -v v5.5.0-RC2)
  • Catalyst (Catalyst/generate-tarballs.sh v5.5.0-RC2)
• Upload source tarballs to paraview.org
  • rsync -rptv $tarballs paraview.release:ParaView_Release/v5.5/
• Build binaries from superbuild
  • Update the superbuild to build from the release tarballs
  • Create a paraview-superbuild merge request targeting release
  • Build binaries (Do: test)

Validating binaries

• Python
• import compiler
• import numpy
• Plugins are present and load properly
• Text source LaTeX $A^2$
• OSPRay
• AutoMPI

Merge superbuild MR and tag

• Do: merge if binaries validate successfully
• Update local release branch from origin/release
• git tag -a -m 'ParaView 5.5.0-RC2' v5.5.0-RC2 HEAD
• git push origin v5.5.0-RC2

Upload binaries

• Sign macOS binary
• Upload binaries to paraview.org
  • rsync -rptv $binaries paraview.release:ParaView_Release/v5.5/
• Update md5sum.txt with checksums of new files
• Update https://www.paraview.org/files/listing.txt
• Test download links

Post-release

• Notify paraview@paraview.org and paraview-developers@paraview.org that the release is available.

/cc @ben.boeckel /cc @cory-quammen /cc @utkarsh.ayachit