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

Stargate RC5 Tracking Issue #8104

Closed
clevinson opened this issue Dec 7, 2020 · 2 comments · Fixed by #8156
Closed

Stargate RC5 Tracking Issue #8104

clevinson opened this issue Dec 7, 2020 · 2 comments · Fixed by #8156

Comments

@clevinson
Copy link
Contributor

clevinson commented Dec 7, 2020

Cosmos SDK v0.40 has so far seen 5 release candidates (rc0-rc4). RC3 is the mostly recent RC tagged against master, and RC4 contained only one fix for an issue that was causing upgrade failures on the cosmoshub-testnet-stargate-d.

Below is an overview of all commits into master since v0.40.0-rc3 for the purposes of auditing what changes are coming into a propsective v0.40.0-rc5. The intention is to tag rc5 directly off of master, but if there are commits in this below list that are explicitly outside of the scope of Stargate, we may instead cherry-pick all Stargate commits into a separate release branch.

Checked boxes indicate that the PR has been reviewed for inclusion in v0.40.0.

Missing Changelog

PRs from the above list that warrant an updated changelog entry:

Outstanding Issues

The following issues / PRs are still outstanding or pending merge, and currently blocking an RC5:

@alexanderbez
Copy link
Contributor

Some of these are merged already. Should they be checked off?

@clevinson
Copy link
Contributor Author

clevinson commented Dec 7, 2020

@alexanderbez Everything in the top checkilst is merged in master already. Those checkboxes are for double-checking to make sure there aren't pieces which we want to explicitly exclude from v0.40.0. The ones in the top list still unchecked are items that I'd like to investigate in a bit more detail to ensure that we have a corresponding changelog entry, and if there's a changelog entry that needs adding, I would put it in the second "Missing Changelog" section below.

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 a pull request may close this issue.

3 participants
@clevinson @alexanderbez and others