ParaView is consistently reaching the maximum file path limits on its Windows packaging builds. In order to help reduce this, there’s an idea to migrate to date-based versioning on
master rather than
git describe-based versioning. Example
Before: ParaView-master-5.12.0-RC1-NNN-gXXXXXXXXXX After : ParaView-5.12.YYYYMMDD
NNN is the number of commits since the named tag and
XXXXXXXXXX is a unique git hash prefix. The
YYYYMMDD part is updated every day on ParaView
master to the current day. As you can see, this should give us at least 19 characters of breathing room (~7.5%) for our longer paths again (it could be more as the
XXXXXXXXXX length depends on the size of ParaView’s history; currently Git uses 10 characters).
Note that non-
master builds will continue to use
git describe as otherwise all builds would appear as
5.12.0-RC1 which is too confusing.
- Version number is ambiguous within a day. Not an issue with “I’m getting a nightly”, but could be confusing given MR and arbitrary
releasebuilds and MRs will continue to fail to build Windows
.msibinaries until the tag arrives and removes the
-NNN-gXXXXXXXXXXsuffix to make filenames short enough
- Shorter version names.
masterbuilds can complete
.msibuilds and test.
- Deprecations on
releaseversions can now fire on
masteras the deprecation macros can detect “5.12-relevant” from “will be 5.13” while keeping a monotonic property for versioning.
A prior discussion was had, but nothing was actually done post-5.11 at the time.
- ParaView: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6585
- ParaView Superbuild: https://gitlab.kitware.com/paraview/paraview-superbuild/-/merge_requests/1137