2.4.0 tag commit

[durack1]

@doutriaux1 @aashish24 might I suggest the following step-by-step is undertaken for 2.4.0 tagging? This should clear up some of the issues that have popped up with 2.2.0:

• [x] Validate version info is correctly written (UV-CDAT version should be 2.4.0)
• [x] Prepare and publish release notes (e.g. v2.2.0)
• [x] Update dependencies so that checkout tag points are set and match 2.4.0 release: CMOR_BRANCH="uvcdat-2.4.0"; LIBCDMS_BRANCH="uvcdat-2.4.0"; VISTRAILS_BRANCH="uvcdat-2.4.0"; VTK_BRANCH="uvcdat-2.4.0"; UVCMETRICS_BRANCH="uvcdat-2.4.0"
• [x] Update README.md with updated Stable version info (should be 2.4.0)
• [x] Set 2.4.0 tag point for UV-CDAT/uvcdat repo
• [x] Obtain Zenodo DOI
• [x] Finalise README.md with updated Zenodo DOI info
• [x] Move 2.4.0 tag point to new commit
• [x] Update wiki so correct tag points (2.4.0) are noted for build notes: linux, MacOS X etc
• [x] After 2.4.0 tag point set, reset all master checkout tag points to point back to uvcdat-master tags (PARAVIEW_BRANCH="uvcdat-master" etc)
• [x] Increment uvcdat-master to 2.5.0 (odd minor [major.minor.patch] number indicating development version)

@doutriaux1 were there any other steps that aren't included above, if so please add/edit..

[doutriaux1]

no worries @chaosphere2112, it's a 15mn job top.