Document Release Workflow #55
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bourque
requested review from
sdhoyt,
greglucas,
tech3371,
bryan-harter,
laspsandoval,
GFMoraga and
maxinelasp
laspsandoval
pushed a commit
to laspsandoval/imap_processing
that referenced
this pull request
Nov 15, 2023
…ument-release-workflow Document Release Workflow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Summary
Overview
This PR updates the
Release Workflowsection of the docs to document our release procedure (as best we can currently) in preparation for SIT-2.I am not super familiar with how software gets from GitHub to an actual 'production environment' on AWS, and if there are any more steps needed than what is described here. It would be helpful to know if I am missing anything!
Updated Files
release-workflow.rst