docs(maintainers): visual representation of release process #2399
Conversation
This file contains hidden or 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
* develop: chore(ci): fix PR labeling permission scope (aws-powertools#2396) chore(ci): document all github action workflows and enforce least-privilege (aws-powertools#2395)
heitorlessa
requested review from
leandrodamascena
and removed request for
a team
boring-cyborg
bot
added
github-actions
pull-request-size
bot
added
the
size/L
github-actions
bot
added
the
documentation
leandrodamascena
approved these changes
Jun 7, 2023
sthulb
pushed a commit
that referenced
this pull request
Jun 19, 2023
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.
Issue number: #2398
Summary
Add visual representation for release, and fix SAR dependency to benefit from Canary testing before SAR deployments.
Changes
User experience
gantt title Release process dateFormat HH:mm axisFormat %H:%M Release commit : milestone, m1, 10:00,2m section Seal Bump release version : active, 8s Prevent source tampering : active, 43s section QA Quality checks : active, 2.2m section Build Checksum : active, 8s Build release artifact : active, 39s Seal : active, 8s section Release Checksum : active, 8s PyPi temp credentials : active, 8s Publish PyPi : active, pypi, 10:06, 29s PyPi release : milestone, m2, 10:06,1s section Git release Checksum : active, after pypi, 8s Git Tag : active, 8s Bump package version : active, 8s Create PR : active, 8s section Layer release Build (x86+ARM) : active, layer_build, 10:08, 6m Deploy Beta : active, layer_beta, after layer_build, 6.3m Deploy Prod : active, layer_prod, after layer_beta, 6.3m Layer release : milestone, m3, 10:26,1s section SAR release Deploy Beta : active, sar_beta, after layer_beta, 2.2m Deploy Prod : active, sar_prod, after sar_beta, 2.2m SAR release : milestone, m4, 10:25,1s section Docs Create PR (Layer ARN) : active, after layer_prod, 8s Release versioned docs : active, 2.2m Documentation release : milestone, m4, 10:28,1m section Post-release Close pending issues : active, 8s Release complete : milestone, m6, 10:31,2mChecklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.