Assembly Release QA Steps: Difference between revisions
No edit summary |
|||
Line 34: | Line 34: | ||
===<span style="color:blue">Assembly | ===<span style="color:blue">Assembly Checklist=== | ||
</span> | </span> | ||
[https://docs.google.com/a/ucsc.edu/spreadsheets/d/1DwtQRe-YXEOkcvDIpcTeU2z8hxMw9ylOyMYZum0n3_o/edit?usp=sharing Assembly QA Google Spreadsheet Checklist Template] | [https://docs.google.com/a/ucsc.edu/spreadsheets/d/1DwtQRe-YXEOkcvDIpcTeU2z8hxMw9ylOyMYZum0n3_o/edit?usp=sharing Assembly QA Google Spreadsheet Checklist Template] |
Revision as of 19:02, 25 October 2016
Welcome to the Assembly Release Guide 😀
Page created Fall. 2016 by Cath, Jairo, and ChrisV.
This page is currently a draft in progress.
For now, use Releasing_an_assembly instead.
Introduction
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.
There are two types of assemblies that the QA team will process:
- New species
- New version for existing species
Change happens
Collaboration rocks. Keep me updated!
Editing this wiki will bring gaggles of glittery giggling unicorn-riding leprechauns to you, and they will improvise a dope rap about you that would make Snoop Dog jelly.
Assembly Checklist
Assembly QA Google Spreadsheet Checklist Template This Gspreadsheet corresponds to this Assembly Release Guide.
🔵 Ready to get started? Let's go to Assembly QA Part 1: DEV Steps