Assembly Release QA Steps: Difference between revisions
From Genecats
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 5: | Line 5: | ||
<span style="color:darkorange">Navigation Menu</span> | <span style="color:darkorange">Navigation Menu</span> | ||
:[[Assembly_Release_QA_Steps | Home Page]] | :[[Assembly_Release_QA_Steps | Home Page]] | ||
::[[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]] |
Revision as of 20:32, 5 December 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
INSTRUCTIONS HERE
Important: How to edit this wiki section and maintain sync with spreadsheet template
INSTRUCTIONS HERE
🔵 Ready to get started? Let's go to Assembly QA Part 1: DEV Steps