Assembly Release QA Steps: Difference between revisions

From Genecats
Jump to navigationJump to search
No edit summary
No edit summary
Line 1: Line 1:
Page created Fall. 2016 by Cath , Jairo, and ChrisV.
 
: This page is currently a draft in progress.
: For now, use [[Releasing_an_assembly]] instead.


<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 16: Line 14:


{| class=wikitable width=415 align=center
{| class=wikitable width=415 align=center
|Wrapping of end-quotemark plus &#160:
|Page created Fall. 2016 by Cath , Jairo, and ChrisV.
: "The quick brown fox jumped over the lazy dogs"&#160; (typewriter exercise).
: This page is currently a draft in progress.
: For now, use [[Releasing_an_assembly]] instead.
|}
|}


Revision as of 21:56, 19 September 2016


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)
Page created Fall. 2016 by Cath , Jairo, and ChrisV.
This page is currently a draft in progress.
For now, use Releasing_an_assembly instead.
Retrieved from "https://genomewiki.ucsc.edu/genecats/index.php?title=Assembly_Release_QA_Steps&oldid=2865"