Closed birchamp closed 1 year ago
Here is the "pinned" discord post where I have kept my notes on what to do to release gA. This should be compared with the above for a final checklist.
Release Processes
Note 1: Prerequisites and one time activities are included at the end of this post.
Note 2: Pull Requests (PRs) are the mechanism used to do merges and they should be reviewed. In the below, for the sake of brevity, PRs are not mentioned.
Preconditions
a. The develop branch has all changes merged that are supposed to be in the next release b. QA has signed off on the work c. Release notes are prepared
Tasks
Expected Outcome
Process for Bug Fixes
If a bug is found in production,then:
To incorporate bug fix into develop, do:
@mandolyte , @elsylambert , @Joel-C-Johnson , @birchamp here are the release notes for 0.9. Feel free to edit if required .
gatewayTranslate 0.9
Pleased to announce the first release of gatewayTranslate (v0.9) , an online scripture editor application.
Features:
Release gT prod link: https://gateway-translate.netlify.app/login Looks good.
Release of gatewayTranslate v0.9.x
Preconditions
Tasks
Original Text of Issue
GATEWAYEDIT steps:
Release Steps:
release-v1.0.0
(add as additional branch to Deploy contexts under https://app.netlify.com/sites/gateway-edit/settings/deploys)release-v1.0.0
When QA has OK'd release branch, make final release by merging to main:
release-v1.0.0
branch to main branch.release-v1.0.0
branch to main . New version is v1.0.0 build: ?\