This story was created to track the 9.0.1 final release testing. Notes and other important comments related to the release can be added here. This can also serve as a place to communicate about the release and link issues that may still require attention.

The release candidate downloads have been prepared with the string "9.0.1" in the title. They are available here:

https://bitbucket.org/lorainelab/integrated-genome-browser/downloads/

***Final Release Testing Steps:

1) Make JIRA issue for Final Release Testing. This will hold notes and other info related to the final release testing.

2) Tag all relevant issues with the proper version tag in JIRA ("9.0.1" for now).

3) Assign Subsystem labels when appropriate to the Label field for stories tagged for release. This will help us identify affected subsystems and help us focus our final testing on subsystems that have been most affected during this release.

4) Quickly Prepare Release Documentation Page to help guide testing. This page must be properly configured for each release to pull over JIRA stories with the proper release tag: https://wiki.transvar.org/display/ITD/9.0.1

5) Perform brief re-testing of all JIRA issues that made it into the release. You can use the Release Documentation page configured in step #4 as a guide for this. This will help ensure all issues we are claiming to be fixed are, in fact, fixed on this final build.

6) Follow the General Smoke Testing checklist and necessary Subsystem testing pages on all Operating Systems. This can be seen as a final sanity check to help ensure critical areas haven't been overlooked:
https://wiki.transvar.org/display/ITD/General+Smoke+Testing
https://wiki.transvar.org/display/ITD/Subsystems

7) Test any outstanding issues or follow up on any remaining testing "thoughts". You would be surprised at how many weird things you might find by just following your nose. If you notice an issue, check to see if it is already present on the live version of IGB or if this is a new issue that was the result of a recent code change.

8) Verify Release Documentation page is accurate and properly configured/refreshed. This page will serve as the basis for the release notes.

9) Once you've determined that all issues are properly fixed, and that all affected subsystems and general functions are working properly on all operating systems, the release can be considered stable and you can give the "Green Light" on the release.

10) While the release is being deployed, check the downloads page for anything odd. Once the release is publicly available, quickly retest all issues tagged for the release and retest IGB general functions to ensure that the right build made it to the downloads page.

11) Add release notes to Bioviz page (use the Release Documentation page to guide this).