Assembly Release QA Steps: Difference between revisions
From Genecats
Jump to navigationJump to search
mNo edit summary |
|||
Line 30: | Line 30: | ||
#New species (a species not yet exisiting as a natively-hosted browser in the rr) | #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). | #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 00:12, 28 March 2017
Navigation Menu |
This page is currently a draft in progress. For now, use Releasing an assembly instead.
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 member can follow this guide in unison with a sync'd Google Spreadsheet template.
There are two types of assemblies that the QA team will process:
- 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).
🔵 Ready to get started? Go to Assembly QA Part 1: DEV Steps