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.
 Checklist for the release
This is a strawman for a release checklist.
- VisIt Project Leader announces proposed date for creating the release candidate.
- Release candidate is created using script "mktag".
- Changes are made to accommodate the new release number
- On the trunk:
- The file "Version" is updated for the next release.
- The splash screen is updated for the next release.
- The new release notes file is created for the next release.
- On the RC:
- "build_visit" script is updated to have the VISIT_VERSION variable point at the new release on the RC and merged to the trunk.
- The build_notes (general and Mac) are updated to reference a build_visit that's link is for the current version.
- On the trunk:
- The release candidate is finalized
- Developers put their final fixes (guaranteed to be safe) onto the release candidate
- Each developer makes sure all of their changes are placed into the release notes
- Preliminary builds are made on major platforms.
- The VisIt project leader declares all work on the release candidate should be frozen
- Final builds are made for each platform
- The builds are posted on the web
- The new release is installed at participating sites
- The new release is announced via firstname.lastname@example.org
- The release candidate branch is copied into the tags directory.