Assembly Release QA Steps: Difference between revisions

From Genecats
Jump to navigationJump to search
No edit summary
No edit summary
Line 1: Line 1:
<div style="border: 2px solid #A3B1BF; padding: .5em 1em 1em 1em; border-top: none; background-color: #FFFBF1; color: #000;">
<div style="border: 2px solid #A3B1BF; padding: .5em 1em 1em 1em; border-top: none; background-color: #FFFBF1; color: #000;">


Line 14: Line 13:
# '''New version for exisiting species:''' Assembly version for a species that already exists as a browser.
# '''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  
When a new or updated assembly is ready to QA, the QA team should perform the following steps, outlined in the pages below:
#Perform assembly QA steps
 
#Perform assembly release steps (from dev > beta > public sites)
#Assembly QA Part 1: DEV Steps
#Assembly QA Part 2: BETA Steps
#Assembly QA Part 3: RR Steps
#Assembly QA Part 4: Post Release Steps
 
 




Revision as of 22:16, 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
Retrieved from "https://genomewiki.ucsc.edu/genecats/index.php?title=Assembly_Release_QA_Steps&oldid=2867"