Assembly Release QA Steps: Difference between revisions
No edit summary |
No edit summary |
||
Line 23: | Line 23: | ||
This wiki section exists as a guide for the assembly QA and release process. <br> | This wiki section exists as a guide for the assembly QA and release process. <br> | ||
Note the 4 sections in the Navigation menu at the upper right of this home page. <br> | Note the 4 sections in the Navigation menu at the upper right of this home page. <br> | ||
The QA member can follow this guide in unison with a Google Spreadsheet template. | The QA member can follow this guide through the 4 steps in unison with a Google Spreadsheet template. | ||
Revision as of 21:36, 3 November 2016
Navigation Menu |
Page created Fall. 2016 by Cath, Jairo, and ChrisV.
This page is currently a draft in progress.
For now, use the old wiki instructions for Assembly QA/Release 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
Change happens
Collaboration rocks. Keep me updated!
Editing this wiki will bring gaggles of glittery giggling unicorn-riding leprechauns to you.
🔵 Ready to get started? Let's go to Assembly QA Part 1: DEV Steps