Assembly Release QA Steps: Difference between revisions

From Genecats
Jump to navigationJump to search
No edit summary
Line 19: Line 19:
#Assembly QA Part 3: RR Steps
#Assembly QA Part 3: RR Steps
#Assembly QA Part 4: Post Release Steps
#Assembly QA Part 4: Post Release Steps


๐Ÿ”ตย  Ready to get started? Let's go toย  [[Assembly QA Part 1: DEV Steps]]
๐Ÿ”ตย  Ready to get started? Let's go toย  [[Assembly QA Part 1: DEV Steps]]

Revision as of 22:22, 19 September 2016

Welcome to the Assembly Release: QA Steps page! ๐Ÿ˜€

Page created Fall. 2016 by Cath , Jairo, and ChrisV.
This page is currently a draft in progress.
For now, use Releasing_an_assembly instead.

For the UCSC Genome Browser QA Team, there are two types of genome assemblies:

  1. New species: Assembly for a species that is not already exisiting as a browser.
  2. New version for exisiting species: Assembly version for a species that already exists as a browser.

When a new or updated assembly is ready to QA, the QA team should perform the following steps, outlined in the pages below:

  1. Assembly QA Part 1: DEV Steps
  2. Assembly QA Part 2: BETA Steps
  3. Assembly QA Part 3: RR Steps
  4. Assembly QA Part 4: Post Release Steps


๐Ÿ”ต Ready to get started? Let's go to Assembly QA Part 1: DEV Steps