Making a Release

Here are the steps. Proceed down the list as long as each step succeeds. Any single failure aborts the release process.

1. Update ./ChangeLog. Hopefully, it was kept up-to-date during development.

2. make clean all check

3. Edit ./version to hold the new release's major.minor number.

4. autoconf

5. ./configure

6. make clean all check

7. cvs commit

8. make doc

9. make distclean

10. make dist

11. Take the distribution file to another computer. Do the ./configure; make all check install thang there.

12.     cvs tag release-`cat version |sed -e "s/[.]/-/g"`
    

13. Go to Giggle's Page on SourceForgehttps://sourceforge.net/projects/giggle/, select Admin, then Edit/Release Files. Add a release to package giggle. The new release's name is major.minor. When requested, upload the two archives to upload.sourceforge.netftp://upload.sourceforge.net/. It's an anonymous ftp login, not a Source Forge account login.

14. It appears that Source Forge makes new files available only at certain time periods.^13.1 So don't worry if the files are not visible right away.

15. Use scp to upload the documentation to Giggle's account on Source Forge. That is

      cd doc
      scp index.html gstover@giggle.sourceforge.net:/home/groups/g/gi/giggle/htdocs/index.html
      scp -r giggle gstover@giggle.sourceforge.net:/home/groups/g/gi/giggle/htdocs
    

16. Login into giggle.sourceforge.net with ssh to ensure that the permissions on the documentation files are correct.

      cd /home/groups/g/gi/giggle/htdocs
      chmod 644 index.html
      find giggle -type d -exec chmod 755 {} \; -o -exec chmod 644 {} \;
    

17. Verify the documentation by pointing your Web browser at Giggle's page on Source Forgethttp://giggle.sourceforge.net/.

18. Double-check the Trove categories on the Giggle summary page on Source Forgehttp://sourceforge.net/projects/giggle/.

19. Announce the release.

20. You're done!