-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change to mainnet
and testnet
branch for feature development
#346
Comments
New feature branches must then branch off |
This is our release workflow. The CI/CD will be essential to automating our work. It also means renaming our branches to
|
staging
branch for feature developmentmainnet
and testnet
branch for feature development
@emmacasolin the NAT testing you're currently doing is now just part of local tests stage. However once we adapt the tests to also use the Notice how the these are a separate test stage that occurs after the automatic deployment to AWS. |
If the remote testing The rollback may not need to be done automatically in the case of We could instead just do retries there and then stop if it keeps failing, keeping whatever state of testnet is. However in the case of Since remote tests will involve flaky networking, it's important we put in the necessary retries. |
The fast forward merge between testnet and mainnet can be user-activated, instead of being automatic. This allows us to do any manual work in-between before pressing the big red button. |
Closing as it is done. |
We can build a staging system for PK.
master
tomainnet
testnet
The
testnet
branch is an intermediate branch before merging intomainnet
.This is where we should be branching off features and where we should be cherry picking things.
This is where also the CI/CD must apply QA work to, and it must pass before it gets merged into
mainnet
.Tasks
staging
branch offmaster
nix
job only apply tostaging
branch, thepackages
job still only applies tomaster
staging
as well, since there's alot of tests to run, and many branch commits are obviously not ready. On the other hand, we do want a run over the branches as well. What we can do is to automatically ignoreWIP
commits (prefixed with WIP).The text was updated successfully, but these errors were encountered: