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

Runtime Upgrade v1.3.3 #141

Open
16 tasks
educlerici-zondax opened this issue Oct 11, 2024 · 0 comments
Open
16 tasks

Runtime Upgrade v1.3.3 #141

educlerici-zondax opened this issue Oct 11, 2024 · 0 comments
Assignees
Labels
runtime-upgrade Runtime Upgrade
Milestone

Comments

@educlerici-zondax
Copy link
Contributor

Paseo Testnet Runtime Upgrade Checklist

According to Polkadot fellowship, we need to upgrade for https://github.com/polkadot-fellows/runtimes/releases/tag/v1.3.3

Preparation Tasks

  • Upgrade Proposal Review: Confirm that the core team agreed on the upcoming Runtime Upgrade.
  • Impact Analysis Completed: Which would be the impact of this Runtime Upgrade?.
  • PR Creation:: Run the script to backport the changes from the Polkadot Fellowship Runtime and solve all conflicts.
  • Benchmarking: Run benchmarks according to Paseo hardware specs and upload them as a different PR targeting the previous PR mentioned.
  • Chopsticks testing: Fork Paseo relay-chain and its system chains and commit the targeted runtime upgrade.
    • Epoch and Era changes: Make chopticks to produce the necessary amount of changes to change the Era and assure blocks are still produced.
    • XCM transfers: Make a teleport to the Paseo assethub and PAS reserved transfer to any available parachain.
  • Try-Runtime: Run try-runtime and mke sure that no state inconsistences are reported.
  • Polkadot Fellowship contact: In case of any issues detected during testing, contact any Polkadot Fellowship member to address the concern. If no issues this can just be checked.
  • Runtime upgrade on test instance: Commit the Runtime upgrade on the Paseo test instance and leave it running for a whole day.

Execution

  • DB Backup: Ask any infrastructure provider to produce a backup of the network before commiting the upgrade.
  • Notify Stakeholders: Distribute the communication plan through all relevant channels.
  • Schedule Upgrade Window: Decide on and communicate the upgrade window to all stakeholders. Use always CET Timezone for scheduling or communicating deadlines.
  • Final Pre-Upgrade Check: Conduct a last-minute check to ensure all systems and stakeholders are ready.
  • Commit Upgrade: Initiate the runtime upgrade process according to the planned procedure. Use always CET Timezone for scheduling or communicating deadlines.
  • Monitor Deployment: Closely monitor the network for any immediate issues during the upgrade.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
runtime-upgrade Runtime Upgrade
Projects
Status: In Review
Development

No branches or pull requests

2 participants