Background

VIVO continues to mature its release practices, its coding practices, and its documentation practices.

VIVO creates a new wiki for each major or dot release.  For minor dot releases (1.9.3 for example), additional release notes are placed in the dot release wiki.

Before Release

1. Create a new wiki space for the new release, by copying the previous release's wiki space
2. Create and work documentation issues related to the release.  Solicit reviewers for items "In Review"
3. Create release notes for the release
   1. Hand written with table of contents for major new features and improvements
   2. Automated list of issues resolved in the release from JIRA.  Copy the JIRA report to the end of the release notes page.
   3. Update the contributors to make sure everyone who participated in the release is recognized
4. Incorporate release note content into documentation pages in addition to the release notes as needed (new pages for new features, or additions to existing pages, reshoot screen shots for UI changes, etc.)
5. Catch up the new wiki to the current wiki for documentation done in the current production wiki since the new wiki was created.

With Release

On the day of release:

1. Make a single PDF of the documentation wiki and save it as an attachment on the first page of the wiki
2. Update the VIVO web site to point to the new release and the new documentation
3. Update the VIVO repo README to describe the current release and point at the installation instructions in the current release wiki.
4. Update the Documentation sidebar macro (used in all the documentation wikis) to indicate the current production release.
5. Update the Releases page to indicate the current production release.  This page is inserted into other pages in the wiki