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. DONE. Create a new wiki for the new release. See VIVO 1.10.x Documentation
2. IN PROGRESS.  Create and work documentation issues related to the release.  Solicit reviewers for items "In Review"
   

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project="VIVO" and type="Documentation" and fixVersion = v1.10 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

3. IN PROGRESS Create release notes for the release. See Release Notes
   1. DONE Hand written with table of contents for major new features and improvements
   2. IN PROGRESS Automated list of issues resolved in the release from JIRA.  Copy the JIRA report to the end of the release notes page.
   3. IN PROGRESS Update the contributors to make sure everyone who participated in the release is recognized
4. DONE 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. Update the VIVO web site to point to the new release and the new documentation
2. Update the Documentation sidebar macro (used in all the documentation wikis) to indicate the current production release.
3. Update the Releases page to indicate the current production release.  This page is inserted into other pages in the wiki