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

Add RELEASE_CHECKLIST #463

Merged
merged 4 commits into from
Oct 31, 2023
Merged

Add RELEASE_CHECKLIST #463

merged 4 commits into from
Oct 31, 2023

Conversation

HCastano
Copy link
Collaborator

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:

  • A check for storage migrations, with some details around when and how to do them
    • We're not worrying about this yet, so I've skipped it
  • More details around publishing packages to crates.io
    • We're not doing this at the moment either
  • Some sort of local devnet or cloud based devnet sanity checks, e.g ensuring that
    release candidate binaries actually run for some period of time

Copy link

vercel bot commented Oct 31, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
entropy-core ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 31, 2023 4:20pm

Copy link
Member

@JesseAbram JesseAbram left a 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
Copy link
Member

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)

Copy link
Collaborator Author

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.

@HCastano
Copy link
Collaborator Author

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

This checklist is specific to entropy-core. Any other project should have their own checklist to follow in their respective repos

@HCastano HCastano merged commit ae64653 into master Oct 31, 2023
10 checks passed
@HCastano HCastano deleted the hc-release-checklist branch October 31, 2023 19:03
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