Assembly Release QA Steps: Difference between revisions

From Genecats
Jump to navigationJump to search
No edit summary
No edit summary
Line 7: Line 7:
== Welcome to the '''Assembly Release: QA Steps''' page! 😀 ==
== Welcome to the '''Assembly Release: QA Steps''' page! 😀 ==


For the UCSC Genome Browser QA Team, <br> there are two types of genome assemblies:
For the UCSC Genome Browser QA Team, there are two types of genome assemblies:
# '''New species:''' Assembly for a species that is not already exisiting as a browser.
# '''New species:''' Assembly for a species that is not already exisiting as a browser.
# '''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
#Perform assembly QA steps
#Perform assembly release steps (from dev > beta > public sites)
{| class=wikitable width=415 align=center
|Wrapping of end-quotemark plus &#160:
: "The quick brown fox jumped over the lazy dogs"&#160; (typewriter exercise).
|}





Revision as of 21:55, 19 September 2016

Page created Fall. 2016 by Cath , Jairo, and ChrisV.

This page is currently a draft in progress.
For now, use Releasing_an_assembly instead.

Welcome to the Assembly Release: QA Steps page! 😀

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

  1. Perform assembly QA steps
  2. Perform assembly release steps (from dev > beta > public sites)
Wrapping of end-quotemark plus &#160:
"The quick brown fox jumped over the lazy dogs"  (typewriter exercise).