Assembly Release QA Steps: Difference between revisions

From Genecats
Jump to navigationJump to search
mNo edit summary
mNo edit summary
Line 22: Line 22:
a member of the QA team will QA and release the assembly. <br>
a member of the QA team will QA and release the assembly. <br>
This wiki section exists as a guide for the assembly QA and release process. <br>
This wiki section exists as a guide for the assembly QA and release process. <br>
</br>
Note the 4 sections in the Navigation menu at the upper right of this home page. <br>
Note the 4 sections in the Navigation menu at the upper right of this home page. <br>
The QA member can follow this guide in unison with a sync'd Google Spreadsheet template.
</br>
 
The QA rock star can follow this guide in unison with a sync'd Google Spreadsheet checklist,
 
where these wiki steps are automatically populated in the spreadsheet, and therefore will  
There are two types of assemblies that the QA team will process:
always be in sync with the wiki.  
#New species (a species not yet exisiting as a natively-hosted browser in the rr)
#New version for existing species (A new assembly version for a species that already has at least one version in the rr).





Revision as of 02:04, 24 May 2017

Navigation Menu

Home Page
Assembly QA Part 1: DEV Steps
Assembly QA Part 2: Track Steps
Assembly QA Part 3: BETA Steps
Assembly QA Part 4: RR Steps


See also: Releasing an assembly (old steps)


Introduction

When a developer is ready for a new assembly to be released,
a member of the QA team will QA and release the assembly.
This wiki section exists as a guide for the assembly QA and release process.

Note the 4 sections in the Navigation menu at the upper right of this home page.

The QA rock star can follow this guide in unison with a sync'd Google Spreadsheet checklist, where these wiki steps are automatically populated in the spreadsheet, and therefore will always be in sync with the wiki.


🔵 Ready to get started? Go to Assembly QA Part 1: DEV Steps