One of the issues that has plagued me when trying to build tagged releases is that the build always winds up with a version number of xx.0.0, which never matches the tagged version number I’ve checked out. For example, if I check out and build v19.1.2, all commands return 19.0.0, pbs_version in $PBS_HOME says 19.0.0, and any RPMs I build are versioned at 19.0.0.
I propose we automate the process with a git hook that will update all of the appropriate files (configure.ac, pbspro.spec, etc.) when a new tag is added. The hook could also be expanded to do other things as well if you are manually doing things from tag release to tag release, such as building and updating binaries for download on pbspro.org.
I realize after digging through the files that you can override the version number with a configure option (./configure PBS_VERSION=19.1.2) but that is only documented in one place that I’ve found - configure.ac. Neither confluence nor pbspro/INSTALL document it. In any case, I would expect that overriding what is in configure.ac should be the exception in order to test or do a custom build, and not the rule.