From VisItusers.org

The VisIt release process typically takes place every 3-4 months, depending on the complexity of the enhancements and bug-fixes going into a release. This page will eventually describe the procedure that is followed for releasing a new version of VisIt as well as a check list template that can be used to track the progress of items within the release process.

[edit] Checklist for the release

This is a strawman for a release checklist.

1. VisIt Project Leader announces proposed date for creating the release candidate.
2. Release candidate is created using script "mktag".
3. Changes are made to accommodate the new release number
   • On the trunk:
     1. The file "Version" is updated for the next release.
     2. The splash screen is updated for the next release.
     3. The new release notes file is created for the next release.
   • On the RC:
     1. "build_visit" script is updated to have the VISIT_VERSION variable point at the new release on the RC and merged to the trunk.
     2. The build_notes (general and Mac) are updated to reference a build_visit that's link is for the current version.
4. The release candidate is finalized
   1. Developers put their final fixes (guaranteed to be safe) onto the release candidate
   2. Each developer makes sure all of their changes are placed into the release notes
   3. Preliminary builds are made on major platforms.
5. The VisIt project leader declares all work on the release candidate should be frozen
6. Final builds are made for each platform
7. The builds are posted on the web
8. The new release is installed at participating sites
9. The new release is announced via visit-users@ornl.gov
10. The release candidate branch is copied into the tags directory.