Assembly Release QA Steps: Difference between revisions
| Line 24: | Line 24: | ||
There are two types of assemblies that the QA team will process: | There are two types of assemblies that the QA team will process: | ||
#New species | #New species (a species not yet exisiting as a natively-hosted browser in the rr) | ||
#New version for existing species | #New version for existing species (A new assembly version for a species that already has at least one version in the rr). | ||
Revision as of 19:05, 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 (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).
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
- Gspreadsheet "Assembly Checklist Template"
- This template corresponds to the Assembly Release Guide wiki.
- Copy and paste this read-only template to create your own "assembly release checklist."
🔵 Ready to get started? Let's go to Assembly QA Part 1: DEV Steps
