Nightly names with current release version are confusing

Maybe the confusion is that it is not clear if this nightly is before 5.10 or after 5.10:
ParaView-5.10.0-454-g5ee5bdfe50-MPI-Windows-Python3.9-msvc2017-AMD64.exe

How about if we rename this as:
ParaView-after-5.10.0-454-g5ee5bdfe50-MPI-Windows-Python3.9-msvc2017-AMD64.exe

or
ParaView-nightly-after-5.10.0-454-g5ee5bdfe50-MPI-Windows-Python3.9-msvc2017-AMD64.exe

Using the next version would mean that we know ahead of time what the next version is.
Is it 5.11 or is it 5.10.1?

Dan

That fixes the tarball, but the titlebar and about dialog won’t know that.

Depends on which branch you’re on :slight_smile: .

This gives me the idea: why not just put the branch name after ParaView? The build can extract this information easily enough (tarballs are out-of-luck, but that’s not new for untagged releases) and put it into the title bar too. Examples:

ParaView-master-5.10.0-454-g5ee5bdfe50
ParaView-release-5.10.0-10-gdeadbeef
1 Like

This is an improvement. Let’s try it.

1 Like

MR for ParaView’s titlebar: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5440

See results here (word wrapped; the newline in the middle is just a space): https://gitlab.kitware.com/paraview/paraview/-/jobs/6494437#L1108

MR for ParaView superbuild to rename the package: https://gitlab.kitware.com/paraview/paraview-superbuild/-/merge_requests/953

Results will be here: https://gitlab.kitware.com/paraview/paraview-superbuild/-/jobs/6494585

No, there isn’t. It could be dropped in there through the source tarball generator script. Dropping it for all submodules would be handy. But, it is gnarly in there; git archive and submodules work as well together as two rabid territorial badgers in a tiny cage.

1 Like