Paraview GitHub source does not define releases
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
Paraview GitHub source does not clearly define releases
For people who need to edit paraview source code using the github repository there should be git tags for all the paraview source code that is put in a release. Currently there are no tags in the git submodules Utilities/VisItBridge, ThirdParty/protobuf/vtkprotobuf, ThirdParty/IceT/vtkicet, and ThirdParty/QtTesting/vtkqttesting, and the tags in submodule VTK do not correspond with the paraview tags. I'd guess there a method used to know where the sources for a paraview release came from, but it's not using the obvious git tagging method. This is a feature request for the paraview build system. Add consistent git tags to define a release. Currently a developer from another planet (me not in the paraview click, an outsider) can't quickly determine the files in a paraview release using standard git methods.