Deploy C&E MVP to production
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 0
- Avg merge
- 20h 8m
- Merged PRs (30d)
- 30
Description
Once the ETL and MVP feature tickets are deployed to Test env and regression testing is complete, deploy to production
Acceptance Criteria:
- If something breaks as a results of deployment, create separate ticket(s).
- Will need to coordinate time to schedule deployment with Ansley
- Regression testing will need to be complete prior to deploying to PROD.
Additional Comments:
- there could be some merge conflicts with this so making the estimate slightly higher (2 vs 1).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by checking that the ETL and MVP feature tickets are deployed to the Test environment and that regression testing is complete. Review the deployment coordination details with Ansley; done means the MVP is deployed to production, with separate tickets created for any deployment-related breakage.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100