-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add RELEASE_CHECKLIST
#463
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, obvi the benchmark stuff needs to change eventually and maybe it is worthwhile to add entropy js and devops checklist to this, also ok to keep it just for core if that is what the team prefers
- [ ] If an existing call/extrinsic has changed (new pallet index, new call index, parameter changes, | ||
etc.), bump `transaction_version` and bump `spec_version` | ||
- [ ] If you're confused about what to bump, read [this](https://paritytech.github.io/polkadot-sdk/master/sp_version/struct.RuntimeVersion.html) | ||
- [ ] Update runtime benchmarks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe a TODO here that we need to build these on a dedicated machine (we have not setup that dev flow yet in our backlog)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not going to add a TODO
since since this needs to reflect the current state, but I did open #464.
This checklist is specific to |
This adds the first version of our step-by-step process for making
entropy-core
releases.A few things that are missing which we should add in the future:
release candidate binaries actually run for some period of time