Assembly Release QA Steps: Difference between revisions

From Genecats
Jump to navigationJump to search
No edit summary
No edit summary
 
(121 intermediate revisions by the same user not shown)
Line 1: Line 1:
Page created Fall. 2016 by Cath , Jairo, and ChrisV.  
<div style="border: 2px solid #A3B1BF; padding: .5em 1em 1em 1em; border-top: none; background-color: #FFFEFB; color: #000;">
: This page is currently a draft in progress.
 
: For now, use [[Releasing_an_assembly]] instead.
{| class=wikitable width=415 align=right
|
<span style="color:darkorange">Navigation Menu</span>
:[[Assembly_Release_QA_Steps | Home Page]]
::[[Assembly QA Part 1 DEV Steps | Assembly QA Part 1: DEV Steps]]
::[[Assembly QA Part 2 Track Steps | Assembly QA Part 2: Track Steps]]
::[[Assembly QA Part 3 BETA Steps | Assembly QA Part 3: BETA Steps]]
::[[Assembly QA Part 4 RR Steps | Assembly QA Part 4: RR Steps]]
|}
 
 
<span style="color:olive">See also: [[Releasing_an_assembly | Releasing an assembly (old steps)]] </span>
 
 
 
===<span style="color:dodgerblue">Introduction===
</span>
 
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.  
 
 
The QA rock star can follow this guide in unison with a sync'd Google spreadsheet checklist, simply by copying the [http://genomewiki.ucsc.edu/genecats/index.php/Assembly_QA_Part_1_DEV_Steps#Setup:_Create_a_Google_spreadsheet_checklist_from_a_template super fancy-pants spreadsheet template]. These wiki steps are automatically populated in the spreadsheet as a checklist, and therefore will always be in sync with the wiki.  


<div style="border: 2px solid #A3B1BF; padding: .5em 1em 1em 1em; border-top: none; background-color: #FFFBF1; color: #000;">


== Welcome to the '''Assembly Release: QA Steps''' page! 😀 ==
🔵  Ready to get started? Go to  [[Assembly QA Part 1 DEV Steps | Assembly QA Part 1: DEV Steps ]]
 


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 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).
|}




Line 49: Line 60:




[[Category:Browser QA Assembly Release Guide]]
[[Category:Browser QA]]
[[Category:Browser QA]]
[[Category:Browser QA New Assembly]]
[[Category:Browser QA New Assembly]]

Latest revision as of 23:21, 20 March 2018

Navigation Menu

Home Page
Assembly QA Part 1: DEV Steps
Assembly QA Part 2: Track Steps
Assembly QA Part 3: BETA Steps
Assembly QA Part 4: RR Steps


See also: Releasing an assembly (old steps)


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.


The QA rock star can follow this guide in unison with a sync'd Google spreadsheet checklist, simply by copying the super fancy-pants spreadsheet template. These wiki steps are automatically populated in the spreadsheet as a checklist, and therefore will always be in sync with the wiki.


🔵 Ready to get started? Go to Assembly QA Part 1: DEV Steps

Retrieved from "https://genomewiki.ucsc.edu/genecats/index.php?title=Assembly_Release_QA_Steps&oldid=4642"