Assembly Release QA Steps: Difference between revisions
From Genecats
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
|} | |} | ||
<span style="color: | <span style="color:olive">This page is currently a draft in progress. For now, use [[Releasing_an_assembly | Releasing an assembly]] instead.</span> | ||
</span> | |||
===<span style="color:dodgerblue">Introduction=== | ===<span style="color:dodgerblue">Introduction=== |
Revision as of 21:46, 3 November 2016
Navigation Menu |
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,
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.
Note the 4 sections in the Navigation menu at the upper right of this home page.
The QA member can follow this guide through the 4 steps in unison with a Google Spreadsheet template.
There are two types of assemblies that the QA team will process:
- New species (a species not yet exisiting as a natively-hosted browser in the rr)
- New version for existing species (A new assembly version for a species that already has at least one version in the rr).
Understanding the Google Spreadsheet Template for QA Assembly Release
Spreadsheet template: QA Assembly Release
- Gspreadsheet "Assembly Checklist Template"
- NOTE TO SELF - NEED TO PUT TEMPLATE INSTRUCTIONS HERE
Important: Wiki editing structure, maintain spreadsheet checklist sync
INSTRUCTIONS HERE
🔵 Ready to get started? Let's go to Assembly QA Part 1: DEV Steps