Assembly Release QA Steps: Difference between revisions
From Genecats
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
#[[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]] | ||
|} | |||
| | |||
:one | |||
#two | |||
#3 | |||
#4 | |||
#5 | |||
|} | |} | ||
Revision as of 16:02, 18 October 2016
Welcome to the Assembly Release: QA Guide 😀
|
- one
- two
- 3
- 4
- 5
|}
Page created Fall. 2016 by Cath, Jairo, and ChrisV.
This page is currently a draft in progress.
For now, use Releasing_an_assembly instead.
When a developer is ready for a new assembly to be released, the QA team (usually an individual of) will QA and release the assembly. This wiki section exists as a guide for the assembly QA and release process.
CHANGE HAPPENS.
As time goes on, please update this section as things change!
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 the following steps, outlined in this guide.
🔵 Ready to get started? Let's go to Assembly QA Part 1: DEV Steps
