temporalio / temporalio/temporal-worker-controller
Systematize release process
Open
Nobody has claimed this yet.
documentation
enhancement
- Dominant language
- Go
- Stars
- 187
- Forks
- 70
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 31
Description
- Cut
release/vMAJOR.MINOR.xbranch from main - Build and push v1.6.x-rcy image to docker and ECR
- Kick off our CICD real cluster pipelines
- Deploy rc to w-internal-test dogfooding environment successfully
- Cut v1.6.0 Github Tag --> triggers docker push
- Upgrade w-internal-test v1.6.0 whenever convenient if at all
- Upgrade w-internal-prod v1.6.0 during reasonable working hours (pages if wrong)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing release branch, Docker/ECR image, CI/CD cluster-pipeline, GitHub tag, and w-internal-test and w-internal-prod deployment entry points. Define the automation or documented workflow around the seven listed steps, with completion shown by a successful release candidate, dogfood deployment, tagged image, and controlled production upgrade.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, github
- Domain
- ci-cd, cloud, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100