Skip to content
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

chore: remove state nodes from standard release process #1665

Merged

Conversation

KolbyML
Copy link
Member

@KolbyML KolbyML commented Feb 3, 2025

What was wrong?

In todays Trin meeting it was agreed to take State nodes out of the standard release process for the time being.

The reason for this is the State Network is not ready for production and being able to iterate quicker should help us launch quicker as we will know if there is an issue quick and hence fix them quicker

How was it fixed?

Comment out the state network code, if someone wants I can remove it, but I thought to keep it as one day the state nodes will join the standard deployment process again

@@ -61,11 +61,11 @@ This step directs Ansible to use the current master version of trin. Read [about
- Run the deployment:
- Trin nodes:
- `ansible-playbook playbook.yml --tags trin`
- State network nodes (check with the team if there is a reason not to update them):
<!-- - State network nodes (check with the team if there is a reason not to update them):
- Recently, we don't regularly deploy state bridge nodes (because they run for a long time and we don't want to restart them). To deploy all other state nodes, use following command:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I believe that we can also remove lines 65:67.

@KolbyML KolbyML force-pushed the remove-state-from-standard-release-process branch from 4bb6481 to edd3e3f Compare February 3, 2025 23:36
@KolbyML KolbyML merged commit 3b5056d into ethereum:master Feb 4, 2025
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants