Assembly Release QA Steps: Difference between revisions

From Genecats
Jump to navigationJump to search
mNo edit summary
mNo edit summary
Line 12: Line 12:




<span style="color:olive">This page is currently a draft in progress. For now, use [[Releasing_an_assembly | Releasing an assembly]] instead.</span>
<span style="color:olive">See also: [[Releasing_an_assembly | Releasing an assembly (old steps)]] </span>





Revision as of 23:14, 23 May 2017

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.
Note the 4 sections in the Navigation menu at the upper right of this home page.
The QA member can follow this guide in unison with a sync'd Google Spreadsheet template.


There are two types of assemblies that the QA team will process:

  1. New species (a species not yet exisiting as a natively-hosted browser in the rr)
  2. New version for existing species (A new assembly version for a species that already has at least one version in the rr).


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