Description: Run bin/h5vers script to change version to 1.6.0-post0
after creating release tar ball and tagging the release.
Modified HISTORY.txt and RELEASE.txt for
1.6.0-post0
1.6 branch is open for checking in source code.
Solution:
Platforms tested:
Misc. update:
Description: I created released tar ball with bin/release; now I am commiting
files that were updated by the script before tagging the release.
Solution:
Platforms tested:
Misc. update:
Description: Changed version number to be 1.6.0 with empty substring
for the release
Solution: Used bin/h5vers -s 1.6.0 to update all necessary files.
Platforms tested: verbena
Misc. update:
update for release
Description:
Set the version information to 1.6.0-pre1 to get ready for
v1.6 release.
Platforms tested:
h5committested.
Misc. update:
Purpose: Maintenance
Description: Bumped the version number to 1.5.62 after creating
a tar ball for the fourth round of testing.
Solution: run bin/h5vers -s scipt on arabica
Platforms tested: N/A
Misc. update:
Purpose: Maintenance for the third round of testing
Description: Increased the version number to 1.5.59 after creating
a tar ball for testing.
Solution:
Platforms tested:
Misc. update:
Purpose: Maintenance for the second round of testing
Description: Used bin/h5vers to change version number to 1.5.55
Solution:
Platforms tested: arabica
Misc. update:
Purpose: Maintenance
Description: I changed release version to 1.5.54.
Email about tetsing of 1.5.53 will be send after this checkins.
Solution: used bin/h5vers -s to change the version number
Platforms tested: Done on arabica
Misc. update:
Purpose:
To clarify where INSTALL files are located.
Description:
The README.txt refers to the INSTALL files as though they
were in the top HDF5 directory. They are not there so this
was confusing to users. Added a line saying they were located in
the release_docs/ directory.
